CVE-2024-35880
Description
CVE-2024-35880 is a vulnerability in the Linux kernel's io_uring subsystem, specifically related to how kernel buffers (kbuf) are handled during memory mapping (mmap) operations. The flaw stems from a situation where a buffer can be unregistered prematurely while it is still being used, leading to a potential use-after-free issue.
The io_uring mechanism uses the Read-Copy-Update (RCU) method to manage buffers during mmap. However, the absence of a strong reference to the buffer during operations allows it to be unregistered while still in use.
This can result in memory dereferencing errors, leading to crashes or unpredictable behavior.
Statement
This vulnerability is rated as Moderate severity because exploitation requires an attacker to possess local access to execute arbitrary system calls on the host, preventing remote exploitation. In Red Hat Enterprise Linux environments, an unprivileged local user could potentially trigger memory corruption or a denial of service by racing buffer unregistration against memory mapping operations within the io_uring subsystem. Because the issue cannot be triggered across the network and requires specific local concurrency, the overall impact remains limited to local disruption.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.5 | 5.5 | 7.8 |
| Attack Vector | Local | Local | Local |
| Attack Complexity | Low | Low | Low |
| Privileges Required | Low | Low | Low |
| User Interaction | None | None | None |
| Scope | Unchanged | Unchanged | Unchanged |
| Confidentiality | None | None | High |
| Integrity Impact | None | None | High |
| Availability Impact | High | High | High |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
cve.org: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Memory
If the expired pointer is used in a read operation, an attacker might be able to control data read in by the application.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
If the expired pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
If the expired pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.