CVE-2026-90241iommu/vt-d: Tear down scalable-mode context on probe failure
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 8.2 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Sep 18, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | 301f1a80487fd2f51012533792583d4425e8b8c0 builds before 25ac85a9747cd63e1d166ace7b360a2cd9479d9d; from 301f1a80487fd2f51012533792583d4425e8b8c0 before d0e978ced7429b516358bb4d41d337214768ae98; from 301f1a80487fd2f51012533792583d4425e8b8c0 before db5daf25f754cdc20c18525adb88240ece6fdee9; from 301f1a80487fd2f51012533792583d4425e8b8c0 before c509fb73a1093a15accd7d43a61645d4b520f6ac | CNA record |
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
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.