# CVE-2024-0193: Kernel: netfilter: use-after-free in nft_trans_gc_catchall_sync leads to privilege escalation

> A use-after-free in the Linux kernel netfilter subsystem allows local users with CAP_NET_ADMIN to escalate privileges.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Jan 2024
- **Updated:** 4 Mar 2026
- **Also known as:** BELL-CVE-2024-0193, CVE-2024-0228, DEBIAN-CVE-2024-0193, GHSA-52x7-wcqq-wfjp, UBUNTU-CVE-2024-0193

## What is CVE-2024-0193?

CVE-2024-0193 is a high-severity use after free vulnerability in Linux kernel, published on 2 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2024-0193?

It affects 22 products.


Products: Linux kernel, Redhat Codeready Linux Builder, Redhat Codeready Linux Builder for Eus, Redhat Codeready Linux Builder for Ibm Z Systems, Redhat Codeready Linux Builder for Ibm Z Systems Eus, Redhat Codeready Linux Builder for Power Little Endian, Redhat Codeready Linux Builder for Power Little Endian Eus, Redhat Enterprise Linux, Redhat Enterprise Linux for Arm 64, Redhat Enterprise Linux for Arm 64 Els, Redhat Enterprise Linux for Arm 64 Eus, Redhat Enterprise Linux for Els, Redhat Enterprise Linux for Eus, Redhat Enterprise Linux for Ibm Z Systems, Redhat Enterprise Linux for Ibm Z Systems Els, Redhat Enterprise Linux for Ibm Z Systems Eus, Redhat Enterprise Linux for Power Little Endian Els, Redhat Enterprise Linux for Power Little Endian Eus, Redhat Enterprise Linux for Update Services for Sap Solutions, Redhat Enterprise Linux Server Aus and 2 more.

## How do I fix CVE-2024-0193?

Apply the vendor's patch.

## Is CVE-2024-0193 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-0193 exists.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-0193 and fix it if it is affected.

What it is: CVE-2024-0193 is a high-severity use after free vulnerability in Linux kernel, published on 2 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-0193 exists.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-0193/ (Markdown: https://insights.sbomify.com/CVE-2024-0193/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-0193
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-0193
- OSV: https://osv.dev/vulnerability/CVE-2024-0193

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-0193/
Summaries are generated and may contain mistakes; the official description above is the record.