CVE-2026-97618
In the Linux kernel, the following vulnerability has been resolved: io_uring/net: don't overconsume buffers when using MSG_TRUNC When a recv/recvmsg is issued with MSG_TRUNC and the incoming packet is larger than the provided buffer, the net layer returns the full length of the packet rather than the number of bytes actually copied into the buffer. As a result, io_uring advances more of the provided buffer ring than was actually filled. Use the actual filled region size to consume the buffer, but still return the full size to preserve MSG_TRUNC semantics. Take care with multishot, because that seems to already truncate the consumption based on the available payload size. This was reported in https://github.com/axboe/liburing/issues/1619. [axboe: fold in size_t unsigned fix]
Affected versions
Linux kernel versions
6.12
and later are affected. Fixed in
6.12.112,
6.18.53,
7.2.7,
7.3-rc3
and their respective stable series.
References
4 totalFrequently asked questions
-
What is CVE-2026-97618?
CVE-2026-97618 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 6.12 onward and has been patched in 6.12.112, 6.18.53, 7.2.7 and others. CVE-2026-97618 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2026-97618?
Yes. CVE-2026-97618 has been patched. Fixed versions include 6.12.112, 6.18.53, 7.2.7 and others. If you are running Linux kernel 6.12 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2026-97618 actively exploited?
No. CVE-2026-97618 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.