CVE-2024-35843: Vulnerability in Linux Linux
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.
AI Analysis
Technical Summary
CVE-2024-35843 is a vulnerability in the Linux kernel's IOMMU (Input-Output Memory Management Unit) VT-d subsystem, specifically in the I/O page fault (iopf) reporting path. The vulnerability arises from a use-after-free condition due to a race between device lookup and device release. The existing implementation locates PCI devices by scanning the entire PCI device list using pci_get_domain_bus_and_slot(), which is inefficient. To improve performance, the lookup was changed to use device_rbtree_find(), which searches a red-black tree of probed devices. However, this introduced a synchronization issue: the device could be released by the IOMMU subsystem after device_rbtree_find() returns but before iopf_get_dev_fault_param() accesses the device, leading to a use-after-free scenario (CWE-416). This can cause kernel crashes or potentially allow an attacker to execute arbitrary code or cause denial of service by exploiting the race condition. The fix involves adding a mutex to synchronize the I/O page fault reporting path and the device release path, preventing the device from being freed while still in use. This lock is designed to have minimal performance impact since conflicts are rare. The CVSS v3.1 base score is 6.8 (medium severity), reflecting that the vulnerability requires local access (AV:L), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), unchanged scope (S:U), limited confidentiality impact (C:L), no integrity impact (I:N), and high availability impact (A:H). No known exploits are reported in the wild yet.
Potential Impact
For European organizations, this vulnerability poses a moderate risk primarily to systems running vulnerable Linux kernel versions with IOMMU VT-d enabled and PCI devices in use. The use-after-free condition can lead to kernel crashes, causing denial of service and potential system instability. In environments where Linux is used for critical infrastructure, cloud services, or virtualization hosts, this could disrupt operations and availability. While the confidentiality impact is limited, the availability impact is high, which is significant for service providers and enterprises relying on Linux-based servers. Attackers with local access could exploit this vulnerability to cause system crashes or potentially escalate privileges if combined with other vulnerabilities. Given the widespread use of Linux in European data centers, telecom infrastructure, and industrial control systems, the vulnerability could affect a broad range of sectors including finance, manufacturing, and government services. However, exploitation requires local access, limiting remote attack vectors. The absence of known exploits reduces immediate risk but patching is important to prevent future attacks.
Mitigation Recommendations
European organizations should prioritize updating Linux kernels to versions that include the fix for CVE-2024-35843. Specifically, ensure that the kernel includes the mutex synchronization in the IOMMU VT-d I/O page fault reporting path. For systems where immediate patching is not feasible, consider the following mitigations: restrict local access to trusted users only, enforce strict access controls and monitoring on systems with IOMMU enabled, and disable VT-d if not required for the workload to reduce attack surface. Additionally, implement kernel crash monitoring and alerting to detect potential exploitation attempts. Organizations should also review their PCI device usage and IOMMU configurations to minimize exposure. Regularly audit and update Linux kernel versions as part of patch management processes. Finally, maintain comprehensive logging and incident response capabilities to quickly identify and respond to any exploitation attempts.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Italy, Spain, Poland
CVE-2024-35843: Vulnerability in Linux Linux
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.
AI-Powered Analysis
Technical Analysis
CVE-2024-35843 is a vulnerability in the Linux kernel's IOMMU (Input-Output Memory Management Unit) VT-d subsystem, specifically in the I/O page fault (iopf) reporting path. The vulnerability arises from a use-after-free condition due to a race between device lookup and device release. The existing implementation locates PCI devices by scanning the entire PCI device list using pci_get_domain_bus_and_slot(), which is inefficient. To improve performance, the lookup was changed to use device_rbtree_find(), which searches a red-black tree of probed devices. However, this introduced a synchronization issue: the device could be released by the IOMMU subsystem after device_rbtree_find() returns but before iopf_get_dev_fault_param() accesses the device, leading to a use-after-free scenario (CWE-416). This can cause kernel crashes or potentially allow an attacker to execute arbitrary code or cause denial of service by exploiting the race condition. The fix involves adding a mutex to synchronize the I/O page fault reporting path and the device release path, preventing the device from being freed while still in use. This lock is designed to have minimal performance impact since conflicts are rare. The CVSS v3.1 base score is 6.8 (medium severity), reflecting that the vulnerability requires local access (AV:L), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), unchanged scope (S:U), limited confidentiality impact (C:L), no integrity impact (I:N), and high availability impact (A:H). No known exploits are reported in the wild yet.
Potential Impact
For European organizations, this vulnerability poses a moderate risk primarily to systems running vulnerable Linux kernel versions with IOMMU VT-d enabled and PCI devices in use. The use-after-free condition can lead to kernel crashes, causing denial of service and potential system instability. In environments where Linux is used for critical infrastructure, cloud services, or virtualization hosts, this could disrupt operations and availability. While the confidentiality impact is limited, the availability impact is high, which is significant for service providers and enterprises relying on Linux-based servers. Attackers with local access could exploit this vulnerability to cause system crashes or potentially escalate privileges if combined with other vulnerabilities. Given the widespread use of Linux in European data centers, telecom infrastructure, and industrial control systems, the vulnerability could affect a broad range of sectors including finance, manufacturing, and government services. However, exploitation requires local access, limiting remote attack vectors. The absence of known exploits reduces immediate risk but patching is important to prevent future attacks.
Mitigation Recommendations
European organizations should prioritize updating Linux kernels to versions that include the fix for CVE-2024-35843. Specifically, ensure that the kernel includes the mutex synchronization in the IOMMU VT-d I/O page fault reporting path. For systems where immediate patching is not feasible, consider the following mitigations: restrict local access to trusted users only, enforce strict access controls and monitoring on systems with IOMMU enabled, and disable VT-d if not required for the workload to reduce attack surface. Additionally, implement kernel crash monitoring and alerting to detect potential exploitation attempts. Organizations should also review their PCI device usage and IOMMU configurations to minimize exposure. Regularly audit and update Linux kernel versions as part of patch management processes. Finally, maintain comprehensive logging and incident response capabilities to quickly identify and respond to any exploitation attempts.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Linux
- Date Reserved
- 2024-05-17T13:50:33.104Z
- Cisa Enriched
- true
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 682d982ac4522896dcbe3629
Added to database: 5/21/2025, 9:08:58 AM
Last enriched: 6/29/2025, 4:27:49 PM
Last updated: 7/30/2025, 11:25:54 AM
Views: 14
Related Threats
CVE-2025-40770: CWE-300: Channel Accessible by Non-Endpoint in Siemens SINEC Traffic Analyzer
HighCVE-2025-40769: CWE-1164: Irrelevant Code in Siemens SINEC Traffic Analyzer
HighCVE-2025-40768: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in Siemens SINEC Traffic Analyzer
HighCVE-2025-40767: CWE-250: Execution with Unnecessary Privileges in Siemens SINEC Traffic Analyzer
HighCVE-2025-40766: CWE-400: Uncontrolled Resource Consumption in Siemens SINEC Traffic Analyzer
MediumActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.