Vulnerability Description
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]
References
- https://git.kernel.org/stable/c/2e70ea75c7bb38a6dc212975f887310f14f7c043
- https://git.kernel.org/stable/c/41d24d2fb168fa05fcaf9ec4e55478411dbbf8e1
- https://git.kernel.org/stable/c/6028b543884f8735e057ec9eea4908cd61cab230
- https://git.kernel.org/stable/c/927d96f91c582b319d104ecf50ec935a8dc29193
FAQ
What is CVE-2026-97618?
CVE-2026-97618 is a documented vulnerability. 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 ...
How severe is CVE-2026-97618?
CVSS scoring is not yet available for CVE-2026-97618. Check NVD for updates.
Is there a patch for CVE-2026-97618?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.