# CVE-2024-43864: net/mlx5e: Fix CT entry update leaks of modify header context

> A use-after-free vulnerability in the Linux kernel's mlx5e driver allows attackers to cause a system panic and denial of service.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Aug 2024
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2024-43864, DEBIAN-CVE-2024-43864, GHSA-69w2-8rxh-w4m7, UBUNTU-CVE-2024-43864

## What is CVE-2024-43864?

CVE-2024-43864 is a critical use after free vulnerability in Linux kernel, published on 20 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

net/mlx5e: Fix CT entry update leaks of modify header context

The cited commit allocates a new modify header to replace the old
one when updating CT entry. But if failed to allocate a new one, eg.
exceed the max number firmware can support, modify header will be
an error pointer that will trigger a panic when deallocating it. And
the old modify header point is copied to old attr. When the old
attr is freed, the old modify header is lost.

Fix it by restoring the old attr to attr when failed to allocate a
new modify header context. So when the CT entry is freed, the right
modify header context will be freed. And the panic of accessing
error pointer is also fixed.

Weakness: CWE-416 (Use After Free)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2024-43864 being exploited?

There is no known exploitation of CVE-2024-43864 in the wild and no public exploit code.

## 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-43864 and fix it if it is affected.

What it is: CVE-2024-43864 is a critical use after free vulnerability in Linux kernel, published on 20 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-43864 in the wild and no public exploit code.

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-43864/ (Markdown: https://insights.sbomify.com/CVE-2024-43864/index.md)
```

## Sources

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

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