CVE-2026-74439iommu/vt-d: Clear Present bit before tearing down scalable-mode context entry
- 9.3CriticalCVSS base score
- 0.20%Exploitation in 30 daysEPSS · top 91% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Clear Present bit before tearing down scalable-mode context entry device_pasid_table_teardown() zeroes the 128-bit scalable-mode context entry with context_clear_entry() while the Present bit is still set. This creates a window where the hardware can fetch a torn entry, with some fields already zeroed while Present is still set, leading to unpredictable behavior or spurious faults. The context-cache invalidation is issued only after the entry has been zeroed, and intel_pasid_free_table() then frees the PASID directory pages, so the IOMMU can keep walking a stale Present=1 entry that points at freed memory. While x86 provides strong write ordering, the compiler may reorder the two 64-bit writes to the entry, and the hardware fetch is not guaranteed to be atomic with respect to multiple CPU writes. Commit c1e4f1dccbe9d ("iommu/vt-d: Clear Present bit before tearing down context entry") fixed this exact pattern in domain_context_clear_one() and the copied-context path, but device_pasid_table_teardown() was not converted. Align it with the "Guidance to Software for Invalidations" in the VT-d spec, Section 6.5.3.3, using the same ownership handshake as the sibling fix: clear only the Present bit, flush it to the IOMMU, perform the context-cache invalidation, and only then zero the rest of the entry.
Timeline
ID reserved
By Linux
Published
- 2 months later
· 2 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | Critical9.3 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | Critical9.3 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.20% · top 91% of all CVEs (18 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.3.
Affected products
- affected 81e921fd321614c2ad8ac333b041aae1da7a1c6d – < e9e83bcfe37dc719182500dd823c03ab57d934f0
- affected 81e921fd321614c2ad8ac333b041aae1da7a1c6d – < 588718101e8449605f1c7e858fecb7cfa701cdab
- affected 81e921fd321614c2ad8ac333b041aae1da7a1c6d – < 7fd4077dc92b91b1b844333c0a06bb9e286db10a
- affected 81e921fd321614c2ad8ac333b041aae1da7a1c6d – < f46452c3df7a8d8a5addc0926e76ef19ea7da0a0
- affected 333fe86968482ca701c609af590003bcea450e8f
- affected 6.8.2 – < 6.9
- affected 6.9
- unaffected < 6.9
- unaffected 6.12.97 – ≤ 6.12.*
- unaffected 6.18.40 – ≤ 6.18.*
- unaffected 7.1.5 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References4
- https://git.kernel.org/stable/c/e9e83bcfe37dc719182500dd823c03ab57d934f0 (opens in a new tab)
- https://git.kernel.org/stable/c/588718101e8449605f1c7e858fecb7cfa701cdab (opens in a new tab)
- https://git.kernel.org/stable/c/7fd4077dc92b91b1b844333c0a06bb9e286db10a (opens in a new tab)
- https://git.kernel.org/stable/c/f46452c3df7a8d8a5addc0926e76ef19ea7da0a0 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-59586 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-74439)Record last updated .