CVE-2026-90241

Vulnérabilité élevée dans Linux (Linux)

CVSS 8.2 · Élevée
EPSS 0.2%
Linux•Linux•Versions : 301f1a80487fd2f51012533792583d4425e8b8c0, 6.9, <25ac85a9747cd63e1d166ace7b360a2cd9479d9d, 6.18.52, <=6.12.*, 7.2.6, <=*, <=7.2.*, <=6.18.*, <6.9, <db5daf25f754cdc20c18525adb88240ece6fdee9, <c509fb73a1093a15accd7d43a61645d4b520f6ac, 0, 6.12.110, <d0e978ced7429b516358bb4d41d337214768ae98, 7.3

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.

Gravité et risque d'exploitation

CVE-2026-90241 obtient un score CVSS de 8.2/10, soit une gravité élevée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.17 %, ce qui la place devant 6.0 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions 301f1a80487fd2f51012533792583d4425e8b8c0, 6.9, <25ac85a9747cd63e1d166ace7b360a2cd9479d9d, 6.18.52, <=6.12.*, 7.2.6, <=*, <=7.2.*, <=6.18.*, <6.9, <db5daf25f754cdc20c18525adb88240ece6fdee9, <c509fb73a1093a15accd7d43a61645d4b520f6ac, 0, 6.12.110, <d0e978ced7429b516358bb4d41d337214768ae98, 7.3) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références