CVE-2026-80547
8.8Linux · Kernel
A race condition in the Linux kernel s390 vfio_ccw driver allows for improper synchronization of asynchronous hardware events, potentially leading to unauthorized system impact.
Executive summary
A vulnerability in the Linux kernel s390 vfio_ccw subsystem allows a local authenticated attacker to achieve elevated privileges or system compromise due to inadequate locking mechanisms.
Vulnerability
The vulnerability is a race condition within the s390 vfio_ccw driver, specifically regarding how the Channel Report Word (CRW) region handles asynchronous hardware events. Because the driver lacked a dedicated lock for these payloads, an attacker with local user privileges can trigger inconsistent states when reading these events, leading to a high-impact security failure.
Business impact
The CVSS score of 8.8 reflects the high severity of this flaw, primarily due to the potential for total system compromise, including confidentiality, integrity, and availability impacts. While the attack requires local access, the scope change (S:C) indicates that an attacker could potentially break out of restricted environments or gain kernel-level control. This poses a significant risk to the stability and security of enterprise infrastructure running affected Linux kernel versions.
Remediation
Immediate Action: Update the Linux kernel to version 6.12.105, 6.18.46, 7.1.10, or later, as these versions contain the necessary locking implementation to resolve the race condition.
Proactive Monitoring: Monitor kernel logs for recurring s390 vfio_ccw driver errors or unexpected system crashes that may indicate exploitation attempts.
Compensating Controls: Restrict local access to systems utilizing the vfio_ccw driver to trusted personnel only, as the vulnerability requires local access to the affected hardware interface.
Exploitation status
Public Exploit Available: Unknown.
Analyst recommendation
Given the potential for full system compromise, administrators should prioritize patching the Linux kernel across all affected environments. Organizations running s390-based hardware should verify their kernel version against the provided fixed releases and schedule maintenance windows to apply the necessary kernel updates to mitigate this high-severity risk.