Security readout for executives and security teams
Plain-English summary
A race condition in Linux Intel VT-d I/O page-fault handling can access a device after its memory is released. Under the scored conditions, a local low-privileged attacker could potentially compromise confidentiality, integrity, and availability. The supplied evidence does not establish real-world exploitation.
Executive priority
Treat as a high-priority maintenance issue on virtualization hosts, device-passthrough systems, and multi-user Linux infrastructure. It is not supported as an emergency internet-wide threat because exploitation is local and unconfirmed. Patch promptly through supported vendor channels, with priority based on IOMMU usage and untrusted local access.
Technical view
CVE-2024-35843 is a CWE-416 use-after-free. A device may leave the probed-device tree after device_rbtree_find() but before iopf_get_dev_fault_param(). The resolution synchronizes I/O page-fault reporting and IOMMU device release with a mutex. CVSS 3.1 is 8.8: local access, low complexity, low privileges, no user interaction, and changed scope.
Likely exposure
Exposure requires Linux systems using the affected Intel VT-d IOMMU page-fault path and a device-release race. The bundle marks Linux affected and lists 6.1, 6.8.2, and 6.9, but its version data is ambiguous and does not provide reliable fixed-version boundaries. Confirm each deployed kernel against vendor guidance and the referenced stable commits.
Exploitation context
The CVSS vector indicates local, low-privileged access rather than remote exploitation. Triggering also depends on a narrow concurrency condition involving device-initiated page faults and IOMMU device release. The bundle reports KEV as false and supplies no evidence of active exploitation or a public exploit.
Researcher notes
The central issue is object lifetime across device_rbtree_find() and iopf_get_dev_fault_param(). Review synchronization coverage in the fault-reporting and release paths, including error handling. The supplied version representation is internally unclear, so avoid deriving precise vulnerable ranges from it. The two kernel stable commits are the strongest supplied remediation references.
Mitigation direction
- Prioritize kernel updates containing the vendor's synchronization fix.
- Check distribution advisories for exact affected and fixed package versions.
- Restrict untrusted local access until affected systems are updated.
- Review passthrough and device-management exposure on high-value virtualization hosts.
Validation and detection
- Inventory kernel versions on systems using Intel VT-d or IOMMU features.
- Compare installed kernels with vendor advisories and referenced stable commits.
- Confirm updated kernels include synchronization between fault reporting and device release.
- Reboot into the corrected kernel and verify the running version.
- Monitor kernel logs for IOMMU faults, crashes, or device-release anomalies.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2024-35843 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H26LinuxCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H2.54.2CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Base CVSS 3.1 score
6.8MediumVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/3d39238991e745c5df85785604f037f35d9d1b15CVE reference, Linux
- https://git.kernel.org/stable/c/def054b01a867822254e1dda13d587f5c7a99e2aCVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.