CVE-2024-35843

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

HIGH
8.8
CVSS Score
Published: May 17, 2024 at 02:40 PM UTC
Updated: August 4, 2026 at 04:06 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 6.8.26.1 ≤ v < 6.8.26.1 ≤ v < 6.91da177e4c3f46.16f4b8d9dbabec631ed7b33f5d5413d86c7134
Vendor states this is fixed in 3d39238991e7 (fixed)
Vendor states this is fixed in 3d39238991e745c5df85785604f037f35d9d1b15 (fixed)
Vendor states this is fixed in def054b01a86 (fixed)
Vendor states this is fixed in def054b01a867822254e1dda13d587f5c7a99e2a (fixed)
Vendor states this is fixed in 6.1 (unaffected)
Vendor states this is fixed in 6.8.2 (unaffected)
Vendor states this is fixed in 6.9 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (2)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/3d39238991e745c5df85785604f037f35d9d1b15
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/def054b01a867822254e1dda13d587f5c7a99e2a

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-416

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card