CVE-2026-89777

8.8

Linux · Kernel

A use-after-free vulnerability exists in the Linux kernel vfio/pci driver due to improper memory handling during initialization failures, potentially allowing local privilege escalation.

Executive summary

A use-after-free vulnerability in the Linux kernel vfio/pci driver could allow a local, authenticated attacker to trigger kernel-level memory corruption and achieve system compromise.

Vulnerability

The vfio_msi_cap_len function fails to clear a pointer to the MSI permission table after an initialization failure. This leaves a dangling pointer in the device structure, which is subsequently reused or double-freed by the kernel, leading to a use-after-free condition.

Business impact

This vulnerability carries a CVSS score of 8.8, indicating a high level of severity. Successful exploitation allows an attacker with low-privileged local access to execute arbitrary code with kernel-level permissions, leading to a complete system compromise, unauthorized data access, and potential denial-of-service via kernel panic.

Remediation

Immediate Action: Update the Linux kernel to the versions specified in the OSV advisory, specifically 5.10.270, 5.15.221, 6.1.188, or 6.6.157, to ensure the dangling pointer is properly cleared.

Proactive Monitoring: Monitor system logs for kernel oops, general protection faults, or KASAN reports that may indicate exploitation attempts targeting the vfio driver.

Compensating Controls: Restrict access to vfio device nodes and general user access to the system, as the exploit requires local, authenticated access to the target environment.

Exploitation status

Public Exploit Available: Unknown.

Analyst recommendation

Given the high CVSS score and the potential for kernel-level code execution, organizations should prioritize patching affected Linux distributions. Administrators must apply the provided kernel updates as soon as they are available in their distribution repositories to mitigate the risk of local privilege escalation.

More Linux CVEs all →

History

CVE Brief tracked this CVE 1 day 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 8.8 (3.1)
  4. Analyst report written
  5. Published in the daily brief high section

Sources