{"api_version":"1","generated_at":"2026-09-25T14:33:02+00:00","cve":"CVE-2026-97618","urls":{"html":"https://cve.report/CVE-2026-97618","api":"https://cve.report/api/cve/CVE-2026-97618.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-97618","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-97618"},"summary":{"title":"io_uring/net: don't overconsume buffers when using MSG_TRUNC","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/net: don't overconsume buffers when using MSG_TRUNC\n\nWhen a recv/recvmsg is issued with MSG_TRUNC and the incoming packet is\nlarger than the provided buffer, the net layer returns the full length\nof the packet rather than the number of bytes actually copied into the\nbuffer.  As a result, io_uring advances more of the provided buffer ring\nthan was actually filled.  Use the actual filled region size to consume\nthe buffer, but still return the full size to preserve MSG_TRUNC\nsemantics.\n\nTake care with multishot, because that seems to already truncate the\nconsumption based on the available payload size.\n\nThis was reported in https://github.com/axboe/liburing/issues/1619.\n\n[axboe: fold in size_t unsigned fix]","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-25 11:17:16","updated_at":"2026-09-25 11:17:16"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/2e70ea75c7bb38a6dc212975f887310f14f7c043","name":"https://git.kernel.org/stable/c/2e70ea75c7bb38a6dc212975f887310f14f7c043","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/6028b543884f8735e057ec9eea4908cd61cab230","name":"https://git.kernel.org/stable/c/6028b543884f8735e057ec9eea4908cd61cab230","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/927d96f91c582b319d104ecf50ec935a8dc29193","name":"https://git.kernel.org/stable/c/927d96f91c582b319d104ecf50ec935a8dc29193","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-97618","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-97618","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected ae98dbf43d755b4e111fcd086e53939bef3e9a1a 927d96f91c582b319d104ecf50ec935a8dc29193 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected ae98dbf43d755b4e111fcd086e53939bef3e9a1a 2e70ea75c7bb38a6dc212975f887310f14f7c043 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected ae98dbf43d755b4e111fcd086e53939bef3e9a1a 6028b543884f8735e057ec9eea4908cd61cab230 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.12","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.53 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.7 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc3 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["io_uring/net.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"927d96f91c582b319d104ecf50ec935a8dc29193","status":"affected","version":"ae98dbf43d755b4e111fcd086e53939bef3e9a1a","versionType":"git"},{"lessThan":"2e70ea75c7bb38a6dc212975f887310f14f7c043","status":"affected","version":"ae98dbf43d755b4e111fcd086e53939bef3e9a1a","versionType":"git"},{"lessThan":"6028b543884f8735e057ec9eea4908cd61cab230","status":"affected","version":"ae98dbf43d755b4e111fcd086e53939bef3e9a1a","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["io_uring/net.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.12"},{"lessThan":"6.12","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.53","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.7","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc3","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.53","versionStartIncluding":"6.12","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.7","versionStartIncluding":"6.12","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc3","versionStartIncluding":"6.12","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/net: don't overconsume buffers when using MSG_TRUNC\n\nWhen a recv/recvmsg is issued with MSG_TRUNC and the incoming packet is\nlarger than the provided buffer, the net layer returns the full length\nof the packet rather than the number of bytes actually copied into the\nbuffer.  As a result, io_uring advances more of the provided buffer ring\nthan was actually filled.  Use the actual filled region size to consume\nthe buffer, but still return the full size to preserve MSG_TRUNC\nsemantics.\n\nTake care with multishot, because that seems to already truncate the\nconsumption based on the available payload size.\n\nThis was reported in https://github.com/axboe/liburing/issues/1619.\n\n[axboe: fold in size_t unsigned fix]"}],"providerMetadata":{"dateUpdated":"2026-09-25T10:22:25.049Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/927d96f91c582b319d104ecf50ec935a8dc29193"},{"url":"https://git.kernel.org/stable/c/2e70ea75c7bb38a6dc212975f887310f14f7c043"},{"url":"https://git.kernel.org/stable/c/6028b543884f8735e057ec9eea4908cd61cab230"}],"title":"io_uring/net: don't overconsume buffers when using MSG_TRUNC","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-97618","datePublished":"2026-09-25T10:22:25.049Z","dateReserved":"2026-09-24T16:01:01.159Z","dateUpdated":"2026-09-25T10:22:25.049Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-25 11:17:16","lastModifiedDate":"2026-09-25 11:17:16","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"97618","Ordinal":"1","Title":"io_uring/net: don't overconsume buffers when using MSG_TRUNC","CVE":"CVE-2026-97618","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"97618","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/net: don't overconsume buffers when using MSG_TRUNC\n\nWhen a recv/recvmsg is issued with MSG_TRUNC and the incoming packet is\nlarger than the provided buffer, the net layer returns the full length\nof the packet rather than the number of bytes actually copied into the\nbuffer.  As a result, io_uring advances more of the provided buffer ring\nthan was actually filled.  Use the actual filled region size to consume\nthe buffer, but still return the full size to preserve MSG_TRUNC\nsemantics.\n\nTake care with multishot, because that seems to already truncate the\nconsumption based on the available payload size.\n\nThis was reported in https://github.com/axboe/liburing/issues/1619.\n\n[axboe: fold in size_t unsigned fix]","Type":"Description","Title":"io_uring/net: don't overconsume buffers when using MSG_TRUNC"}]}}}