CVE-2026-90244

Linux · Kernel

A race condition in the Linux kernel IOMMU subsystem allows concurrent MSI page list access, potentially leading to data corruption or privilege escalation.

Executive summary

A race condition vulnerability in the Linux kernel IOMMU subsystem could allow a local authenticated attacker to achieve code execution or system instability.

Vulnerability

This is a race condition (CWE-362) occurring within the iommu_dma_get_msi_page function, where missing locking mechanisms allow concurrent access to the msi_page_list. An attacker with local, low-privileged access can trigger this condition when multiple devices share a domain, potentially leading to memory corruption.

Business impact

The vulnerability carries a CVSS score of 7.8, indicating a high severity risk. Successful exploitation allows a local attacker to compromise the confidentiality, integrity, and availability of the host system. This could lead to unauthorized data access, system crashes, or escalation of privileges, posing a significant risk to the stability and security of the underlying infrastructure.

Remediation

Immediate Action: Update the Linux kernel to version 6.18.52, 7.2.6, or later, as provided by your distribution vendor.

Proactive Monitoring: Monitor kernel logs for signs of memory corruption or unexpected system reboots, which may indicate an exploitation attempt.

Compensating Controls: Restrict access to system-level interfaces and limit the ability of unprivileged users to interact with VFIO-assigned devices, as this significantly reduces the attack surface for this specific race condition.

Exploitation status

Public Exploit Available: No

Analyst recommendation

Given the potential for privilege escalation and the high CVSS score, administrators should prioritize patching the kernel across all impacted environments. While the attack requires local access, the ability to corrupt kernel memory makes this a high-priority item for any system utilizing VFIO device pass-through configurations.

More Linux CVEs all →

History

CVE Brief tracked this CVE 2 days before it had a CVSS score.

  1. Disclosed CVE record published
  2. Collected by CVE Brief No CVSS score yet; tracked as early warning
  3. CVSS score assigned 7.8 (3.1)
  4. Analyst report written

Sources