Answer in brief
CVE-2026-90241 records a High severity (CVSS 8.2) vulnerability in iommu/vt-d: Tear down scalable-mode context on probe failure. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.2. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=301f1a80487fd2f51012533792583d4425e8b8c0 <25ac85a9747cd63e1d166ace7b360a2cd9479d9d || >=301f1a80487fd2f51012533792583d4425e8b8c0 <d0e978ced7429b516358bb4d41d337214768ae98 || >=301f1a80487fd2f51012533792583d4425e8b8c0 <db5daf25f754cdc20c18525adb88240ece6fdee9 || >=301f1a80487fd2f51012533792583d4425e8b8c0 <c509fb73a1093a15accd7d43a61645d4b520f6ac | 25ac85a9747cd63e1d166ace7b360a2cd9479d9d, d0e978ced7429b516358bb4d41d337214768ae98, db5daf25f754cdc20c18525adb88240ece6fdee9, c509fb73a1093a15accd7d43a61645d4b520f6ac |
| Linux/Linuxgeneric | 6.9 | Not reported |
Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 17, 2026
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.
Quoted source text, attributed separately from HOL analysis.