CVE-2026-90241

published 17 Sep 2026 · updated 15 Nov 2026

iommu/vt-d: Tear down scalable-mode context on probe failure

8.2HighCVSS 8.2EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel db5daf25f754cdc20c18525adb88240ece6fdee9, Kernel 25ac85a9747cd63e1d166ace7b360a2cd9479d9d, Kernel c509fb73a1093a15accd7d43a61645d4b520f6ac and 4 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=301f1a80487fd2f51012533792583d4425e8b8c0 <db5daf25f754cdc20c18525adb88240ece6fdee9, >=301f1a80487fd2f51012533792583d4425e8b8c0 <25ac85a9747cd63e1d166ace7b360a2cd9479d9d, >=301f1a80487fd2f51012533792583d4425e8b8c0 <c509fb73a1093a15accd7d43a61645d4b520f6ac, >=301f1a80487fd2f51012533792583d4425e8b8c0 <d0e978ced7429b516358bb4d41d337214768ae98, =6.9db5daf25f754cdc20c18525adb88240ece6fdee9, 25ac85a9747cd63e1d166ace7b360a2cd9479d9d, c509fb73a1093a15accd7d43a61645d4b520f6ac, d0e978ced7429b516358bb4d41d337214768ae98
linux-kernel: Kernel>=6.19.0 <7.2.6, >=6.9.0 <6.12.110, >=6.13.0 <6.18.527.2.6, 6.12.110, 6.18.52

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-90241 severity on Zeptric[![CVE-2026-90241](https://zeptric.io/badge/cve/CVE-2026-90241.svg)](https://zeptric.io/cve/CVE-2026-90241)