iommu/vt-d: Flush context cache with correct SID when tearing down aliases
CVE-2026-90240 · published 17 Sept 2026
How serious is it
- Severity: high, CVSS score 8.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-90240?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: f90584f4beb84211c4d21b319cc13f391fe9f3c2 to < 3eb6ad14ef359e426cff14942e220de101cdbe84, f90584f4beb84211c4d21b319cc13f391fe9f3c2 to < a803141597d61dc0511f7cd849625e17d042ca8a, f90584f4beb84211c4d21b319cc13f391fe9f3c2 to < 5baddf100b3be730912485648cbaae5e3a251923, f90584f4beb84211c4d21b319cc13f391fe9f3c2 to < c54e4ae971b98e8d650400137d332cee56c03f55
- Linux Linux: 6.11
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
In the Linux kernel, the following vulnerability has been resolved:
iommu/vt-d: Flush context cache with correct SID when tearing down aliases
domain_context_clear_one() and device_pasid_table_teardown() are both
invoked once per DMA alias of a device. Each function locates the context
entry using the bus/devfn pair provided by the pci_for_each_dma_alias()
callback, then calls intel_context_flush_no_pasid(), which constructs a
device-selective context-cache invalidation from info->bus and
info->devfn (that is, always the requester ID of the device itself).
As a result, for every alias other than the device’s own RID, the context
entry that was just cleared in memory is never invalidated in the context
cache. Hardware may continue using that stale cached entry. In the
scalable-mode teardown path, intel_pasid_free_table() can then free the
PASID directory still referenced by that stale entry, allowing the IOMMU
to walk freed memory.
Fix this by passing the source ID of the entry being torn down to
intel_context_flush_no_pasid(), instead of deriving it from @info.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/3eb6ad14ef359e426cff14942e220de101cdbe84
- git.kernel.org/stable/c/a803141597d61dc0511f7cd849625e17d042ca8a
- git.kernel.org/stable/c/5baddf100b3be730912485648cbaae5e3a251923
- git.kernel.org/stable/c/c54e4ae971b98e8d650400137d332cee56c03f55
Merged from CVE List. Last updated 26 Oct 2026. All vulnerabilities · RSS · JSON