CVE-2024-35843
- Source
- https://nvd.nist.gov/vuln/detail/CVE-2024-35843
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-35843.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2024-35843
- Downstream
- Related
- Published
- 2024-05-17T14:40:10.747Z
- Modified
- 2026-01-05T21:27:27.697697Z
- Severity
-
- 6.8 (Medium) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H CVSS Calculator
- Summary
- iommu/vt-d: Use device rbtree in iopf reporting path
- Details
-
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 pcigetdomainbusandslot(). This function searches the list of all PCI devices until the desired device is found. To improve lookup efficiency, replace it with devicerbtree_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 devicerbtreefind() and before iopfgetdevfaultparam(), 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.
- Database specific
{ "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/35xxx/CVE-2024-35843.json", "cna_assigner": "Linux" }- References
-
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- https://git.kernel.org/stable/c/3d39238991e745c5df85785604f037f35d9d1b15
- https://git.kernel.org/stable/c/def054b01a867822254e1dda13d587f5c7a99e2a
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/35xxx/CVE-2024-35843.json
- https://nvd.nist.gov/vuln/detail/CVE-2024-35843
Affected packages
Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected ranges
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced06f4b8d09dbabec631ed7b033f5d5413d86c7134Fixed3d39238991e745c5df85785604f037f35d9d1b15Fixeddef054b01a867822254e1dda13d587f5c7a99e2a