CVE-2026-31774: io_uring/net: fix slab-out-of-bounds read in io_bundle_nbufs()
In the Linux kernel, the following vulnerability has been resolved:
io_uring/net: fix slab-out-of-bounds read in io_bundle_nbufs()
sqe->len is __u32 but gets stored into sr->len which is int. When
userspace passes sqe->len values exceeding INT_MAX (e.g. 0xFFFFFFFF),
sr->len overflows to a negative value. This negative value propagates
through the bundle recv/send path:
1. io_recv(): sel.val = sr->len (ssize_t gets -1)
2. io_recv_buf_select(): arg.max_len = sel->val (size_t gets
0xFFFFFFFFFFFFFFFF)
3. io_ring_buffers_peek(): buf->len is not clamped because max_len
is astronomically large
4. iov[].iov_len = 0xFFFFFFFF flows into io_bundle_nbufs()
5. io_bundle_nbufs(): min_t(int, 0xFFFFFFFF, ret) yields -1,
causing ret to increase instead of decrease, creating an
infinite loop that reads past the allocated iov[] array
This results in a slab-out-of-bounds read in io_bundle_nbufs() from
the kmalloc-64 slab, as nbufs increments past the allocated iovec
entries.
BUG: KASAN: slab-out-of-bounds in io_bundle_nbufs+0x128/0x160
Read of size 8 at addr ffff888100ae05c8 by task exp/145
Call Trace:
io_bundle_nbufs+0x128/0x160
io_recv_finish+0x117/0xe20
io_recv+0x2db/0x1160
Fix this by rejecting negative sr->len values early in both
io_sendmsg_prep() and io_recvmsg_prep(). Since sqe->len is __u32,
any value > INT_MAX indicates overflow and is not a valid length.
Security readout for executives and security teams
Plain-English summary
A low-privileged local user can submit an oversized io_uring length that becomes negative inside the Linux kernel. The resulting processing loop can read beyond an allocated kernel buffer, potentially exposing sensitive memory or crashing the system. Network access alone is insufficient; the attacker needs local execution and access to the affected io_uring path.
Executive priority
Prioritize internet-facing multi-user hosts, shared compute, containers sharing a host kernel, and systems where attackers may gain limited local execution. Treat remediation as high priority, but not as an unauthenticated remote emergency. Confirm distribution-specific applicability before broad deployment.
Technical view
A 32-bit unsigned sqe->len exceeding INT_MAX is stored in a signed int, producing a negative sr->len. Subsequent signed-to-unsigned conversions prevent length clamping. io_bundle_nbufs() then handles 0xFFFFFFFF as -1, causing its loop counter to move incorrectly and read beyond the allocated iovec array. The fix rejects negative lengths during send and receive preparation.
Likely exposure
Exposure is most relevant on systems running an affected Linux kernel where untrusted or compromised local processes can use io_uring bundle send or receive functionality. The supplied affected-version data is ambiguous, including duplicate identifiers and an unexpected "0" entry, so exact distribution package exposure requires vendor confirmation.
Exploitation context
The CVSS vector describes local, low-complexity exploitation requiring low privileges and no user interaction, with potentially high confidentiality and availability impact. The bundle marks this CVE as absent from KEV and provides no evidence of active exploitation, public weaponization, or remote exploitation.
Researcher notes
The observed failure is a slab-out-of-bounds read from kmalloc-64 caused by integer conversion and faulty loop progress. KASAN observed the read in io_bundle_nbufs(). The sources identify rejection of negative sr->len in io_sendmsg_prep() and io_recvmsg_prep() as the correction. No CWE, exploit evidence, or definitive distribution mapping is supplied.
Mitigation direction
Install a distribution kernel containing the applicable referenced stable fix.
Follow Linux distribution guidance to confirm the corrected package and affected version range.
Reboot into the updated kernel after installation.
Where patching is delayed, reduce untrusted local access and review io_uring exposure.
Validation and detection
Record the running kernel version on every potentially exposed system.
Confirm the installed kernel package includes the applicable stable fix commit.
Verify systems rebooted into the corrected kernel rather than retaining the previous kernel.
Review distribution advisories because the supplied affected-version list is not sufficiently precise.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-31774 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
5Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.