CVE-2024-0193VulnerabilityPublished 2 Jan 2024Updated 4 Mar 2026

CVE-2024-0193: Use After Free

Source CVE Database V5

Not known to be exploited · CVSS 7.8 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

7.8High

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

EPSS: 0.8% chance of exploitation in 30 days – higher than 57% 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 2 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 2026-10-26.

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 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-0193, organizations should: 1) Monitor for and apply official Linux kernel patches addressing this vulnerability as soon as they become available from trusted vendors or distributions. 2) Restrict assignment of the CAP_NET_ADMIN capability to only trusted and necessary users or processes, minimizing the attack surface. 3) Employ strict access controls and auditing on systems that allow local user access, especially those with network administration privileges. 4) Use kernel hardening features such as Kernel Address Space Layout Randomization (KASLR) and memory protection mechanisms to reduce exploitation likelihood. 5) Consider container or virtualization isolation to limit the impact of potential privilege escalations. 6) Regularly review and update firewall and network security configurations to detect anomalous behavior potentially related to exploitation attempts. 7) Implement comprehensive monitoring and alerting for suspicious local privilege escalation attempts. 8) Educate system administrators about the risks of granting CAP_NET_ADMIN and the importance of least privilege principles. These steps go beyond generic advice by focusing on capability restriction and proactive patch management tailored to this vulnerability's characteristics.

Description

A use-after-free flaw was found in the netfilter subsystem of the Linux kernel. If the catchall element is garbage-collected when the pipapo set is removed, the element can be deactivated twice. This can cause a use-after-free issue on an NFT_CHAIN object or NFT_OBJECT object, allowing a local unprivileged user with CAP_NET_ADMIN capability to escalate their privileges on the system.

Impact

The primary impact of CVE-2024-0193 is local privilege escalation, allowing an attacker with limited capabilities (CAP_NET_ADMIN) to gain higher privileges, potentially root-level access. This can lead to full system compromise, unauthorized data access, modification, or disruption of services. Since netfilter is integral to Linux networking, exploitation could also affect firewall and packet filtering operations, potentially disrupting network security controls. Organizations relying on Linux servers, network appliances, or embedded devices with netfilter enabled are at risk. The vulnerability could be leveraged to bypass security controls, install persistent malware, or pivot within internal networks. Although remote exploitation is unlikely without local access, insider threats or attackers who have gained initial footholds could exploit this flaw to escalate privileges and deepen their control. The absence of known exploits in the wild currently reduces immediate risk but does not eliminate it, as public disclosure often leads to exploit development. The impact spans confidentiality, integrity, and availability, making it a critical concern for enterprise, cloud, and infrastructure providers.

References

Community reviews

Loading reviews…