PoC Monitor
← All CVEs
CVE-2026-90241published 17 Sep 2026 16:07 UTCData: JSON · API

Linux

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

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.2high · scored by CNA
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Linux Linux
  • >= 301f1a80487fd2f51012533792583d4425e8b8c0, < 25ac85a9747cd63e1d166ace7b360a2cd9479d9d
  • >= 301f1a80487fd2f51012533792583d4425e8b8c0, < d0e978ced7429b516358bb4d41d337214768ae98
  • >= 301f1a80487fd2f51012533792583d4425e8b8c0, < db5daf25f754cdc20c18525adb88240ece6fdee9
  • >= 301f1a80487fd2f51012533792583d4425e8b8c0, < c509fb73a1093a15accd7d43a61645d4b520f6ac

Fixed in 25ac85a9747cd63e1d166ace7b360a2cd9479d9d, d0e978ced7429b516358bb4d41d337214768ae98, db5daf25f754cdc20c18525adb88240ece6fdee9, c509fb73a1093a15accd7d43a61645d4b520f6ac

Linux Linux
  • 6.9

Fixed in 0, 6.12.110, 6.18.52, 7.2.6, 7.3

Mitigation

Upgrade Linux to 25ac85a9747cd63e1d166ace7b360a2cd9479d9d or d0e978ced7429b516358bb4d41d337214768ae98 or db5daf25f754cdc20c18525adb88240ece6fdee9 or c509fb73a1093a15accd7d43a61645d4b520f6ac or later.

Upgrade Linux to 0 or 6.12.110 or 6.18.52 or 7.2.6 or 7.3 or later.

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published17 Sep 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.