# CVE-2024-35843: iommu/vt-d: Use device rbtree in iopf reporting path

> A race condition in the Linux kernel IOMMU driver allows a use-after-free, potentially enabling local attackers to execute code or escalate privileges.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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:** 17 May 2024
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2024-35843, DEBIAN-CVE-2024-35843, GHSA-v44p-g5j5-r658, ROOT-OS-DEBIAN-11-CVE-2024-35843, ROOT-OS-DEBIAN-12-CVE-2024-35843, ROOT-OS-UBUNTU-2204-CVE-2024-35843, UBUNTU-CVE-2024-35843

## What is CVE-2024-35843?

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

### Official description

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

iommu/vt-d: Use device rbtree in iopf reporting path

The existing I/O page fault handler currently locates the PCI device by
calling pci_get_domain_bus_and_slot(). This function searches the list
of all PCI devices until the desired device is found. To improve lookup
efficiency, replace it with device_rbtree_find() to search the device
within the probed device rbtree.

The I/O page fault is initiated by the device, which does not have any
synchronization mechanism with the software to ensure that the device
stays in the probed device tree. Theoretically, a device could be released
by the IOMMU subsystem after device_rbtree_find() and before
iopf_get_dev_fault_param(), which would cause a use-after-free problem.

Add a mutex to synchronize the I/O page fault reporting path and the IOMMU
release device path. This lock doesn't introduce any performance overhead,
as the conflict between I/O page fault reporting and device releasing is
very rare.

Weakness: CWE-416 (Use After Free)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2024-35843 being exploited?

There is no known exploitation of CVE-2024-35843 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-35843 and fix it if it is affected.

What it is: CVE-2024-35843 is a high-severity use after free vulnerability in Linux kernel, published on 17 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-35843 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-35843/ (Markdown: https://insights.sbomify.com/CVE-2024-35843/index.md)
```

## Sources

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

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