CVE-2024-35880: io_uring/kbuf: hold io_buffer_list reference over mmap
In the Linux kernel, the following vulnerability has been resolved:
io_uring/kbuf: hold io_buffer_list reference over mmap
If we look up the kbuf, ensure that it doesn't get unregistered until
after we're done with it. Since we're inside mmap, we cannot safely use
the io_uring lock. Rely on the fact that we can lookup the buffer list
under RCU now and grab a reference to it, preventing it from being
unregistered until we're done with it. The lookup returns the
io_buffer_list directly with it referenced.
Security readout for executives and security teams
Plain-English summary
A flaw in Linux io_uring buffer handling could let a low-privileged local user trigger unsafe memory access during a buffer-backed mmap operation. Successful exploitation could compromise confidentiality, integrity, or availability. It is not remotely exploitable according to the supplied CVSS vector.
Executive priority
Prioritize remediation during the next urgent kernel maintenance cycle, accelerating systems with untrusted local users or sensitive workloads. This is a high-impact local privilege boundary risk, but the supplied evidence does not support emergency treatment based on active exploitation.
Technical view
The io_uring kbuf mmap path could use an io_buffer_list while another operation unregisters it. The fix performs the RCU lookup with a retained reference, preventing the list from being released before mmap finishes. The supplied CVSS 3.1 score is 7.8 with local access, low complexity, low privileges, and no user interaction.
Likely exposure
Exposure requires Linux systems running an affected kernel where an untrusted local account can exercise the vulnerable io_uring buffer-mapping path. The supplied version list identifies affected releases or boundaries including 6.6.26, 6.7, 6.8.5, and 6.9, but its flattened version data is ambiguous. Confirm distribution-specific package status.
Exploitation context
The supplied record does not identify CISA KEV listing, active exploitation, or a public proof of concept. Exploitation requires local access and low privileges. Treat the impact assessment as serious, but do not characterize this vulnerability as exploited in the wild without additional evidence.
Researcher notes
The core issue is lifetime management around io_buffer_list lookup during mmap: RCU lookup alone was insufficient without retaining a reference. The stable commits are authoritative fix references. Exact introduction and fixed-version ranges cannot be reconstructed confidently from the flattened version entries supplied, so downstream advisory mapping is essential.
Mitigation direction
Apply a vendor-supported kernel update containing the referenced io_uring kbuf fix.
Check distribution advisories because packaged kernel versions may not match upstream numbering.
Prioritize multi-user systems where untrusted local users can access io_uring.
If patching is delayed, consult vendor guidance for supported exposure-reduction options.
Validation and detection
Inventory running kernel versions, not only installed kernel packages.
Map each kernel package to its distribution advisory for CVE-2024-35880.
Confirm the running kernel includes the relevant stable fix or vendor backport.
Reboot after updating, then verify the active kernel version.
Review local account exposure and access to affected io_uring functionality.
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-2024-35880 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
2ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
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.