Answer in brief
CVE-2024-35843 records a High severity (CVSS 8.8) vulnerability in iommu/vt-d: Use device rbtree in iopf reporting path. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), linux/linux_kernel (generic), linux/linux_kernel (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), linux/linux_kernel (generic), linux/linux_kernel (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=06f4b8d09dbabec631ed7b033f5d5413d86c7134 <3d39238991e745c5df85785604f037f35d9d1b15 || >=06f4b8d09dbabec631ed7b033f5d5413d86c7134 <def054b01a867822254e1dda13d587f5c7a99e2a | 3d39238991e745c5df85785604f037f35d9d1b15, def054b01a867822254e1dda13d587f5c7a99e2a |
| Linux/Linuxgeneric | 6.1 | Not reported |
| linux/linux_kernelgeneric | >=1da177e4c3f4 <3d39238991e7 | 3d39238991e7 |
| linux/linux_kernelgeneric | >=1da177e4c3f4 <def054b01a86 | def054b01a86 |
Published upstream
May 17, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.