VulnerabilityPublished 16 Jan 2024Updated 20 Nov 2025

CVE-2024-0582: Use After Free

Source CVE Database V5

Not known to be exploited · 12% EPSS · CVSS 7.8 High.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

7.8High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 12.8% chance of exploitation in 30 days – higher than 96% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Jan 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate CVE-2024-0582, organizations should: 1) Apply official Linux kernel patches as soon as they become available from trusted distribution vendors to address the use-after-free flaw in io_uring. 2) Restrict local user access to trusted personnel only, minimizing the risk of exploitation by unprivileged users. 3) Monitor system logs and kernel crash reports for unusual activity or frequent crashes related to io_uring operations. 4) Employ kernel hardening techniques such as enabling kernel lockdown modes or using security modules (e.g., SELinux, AppArmor) to limit the capabilities of local users. 5) Consider disabling io_uring functionality temporarily if it is not required for critical workloads, reducing the attack surface. 6) Conduct regular security audits and vulnerability scans focusing on kernel-level vulnerabilities. 7) Educate system administrators and users about the risks of local privilege escalation vulnerabilities and the importance of timely patching. These steps go beyond generic advice by focusing on access control, monitoring, and temporary feature disablement as practical interim measures.

Description

A memory leak flaw was found in the Linux kernel’s io_uring functionality in how a user registers a buffer ring with IORING_REGISTER_PBUF_RING, mmap() it, and then frees it. This flaw allows a local user to crash or potentially escalate their privileges on the system.

Impact

The impact of CVE-2024-0582 is significant for organizations running Linux systems with io_uring enabled, particularly in multi-user environments such as shared servers, cloud infrastructures, and enterprise data centers. Exploitation can lead to system crashes, resulting in denial of service and potential operational disruption. More critically, the vulnerability may allow local attackers to escalate privileges, compromising system confidentiality and integrity by gaining unauthorized access to sensitive data or administrative functions. This can facilitate further lateral movement, data exfiltration, or persistent control over affected systems. The vulnerability affects the kernel level, which is foundational to system security, thus amplifying the risk. Organizations relying on Linux for critical infrastructure, web hosting, container orchestration, or cloud services are at heightened risk. The absence of known exploits in the wild currently reduces immediate threat but does not diminish the urgency for remediation, as the vulnerability is straightforward to trigger by local users with minimal privileges.

References

Community reviews

Loading reviews…