← All Advisories
Reported from OT-Advisories.com as of

CVE-2026-90241

Last refreshed2026-10-19

Status: UPDATED  |  Advisory ID: CVE-2026-90241

Key Details

CVECVE-2026-90241
CVSS Score / Version
8.2 (High) / CVSS v3.1
Updated2026-10-19
CVSS Vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
CVSS Prose
attack vector is local; attack complexity is low; privileges required is high; user interaction is none; scope is changed; confidentiality impact is high; integrity impact is high; availability impact is high.
Affected products
Linux Kernel

Affected Products, Subsystems & Sectors

VendorProductAffected VersionsPatch Status
LinuxLinux Kernel
SubsystemsOT Supporting Infrastructure
SectorsAll Sectors

What to Know

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. (NVD)

What to Do

Monitor Linux's web page for any future patch releases.

References

SourceReference
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-90241
CVEhttps://www.cve.org/CVERecord?id=CVE-2026-90241
Report compilation © 2026 OT-Advisories.com  ·  CC BY 4.0  ·  Source materials remain the property of their respective publishers as cited.