CVE-2026-80677

driver core: use READ_ONCE() for dev->driver in dev_has_sync_state()

Published Aug 28, 2026 CVSS 3.1 · 7.8 High EPSS < 1% KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

driver core: use READ_ONCE() for dev->driver in dev_has_sync_state()

dev_has_sync_state() reads dev->driver twice without holding
device_lock() -- once for the NULL check and once to dereference
->sync_state. Some callers only hold device_links_write_lock, which
doesn't prevent a concurrent unbind from clearing dev->driver via
device_unbind_cleanup().

Fix it by reading dev->driver exactly once with READ_ONCE(), pairing
with the WRITE_ONCE() in device_set_driver().

Analysis

AI-generated

Technical impact

The vulnerability is a race condition in the Linux kernel’s device model. On calls to dev_has_sync_state(), the dev->driver pointer is read twice without protection by the device_lock(); one read is for a NULL test, the second dereferences the driver structure’s sync_state field. If a concurrent device unbind clears dev->driver while the function is executing, the kernel may dereference a stale or freed pointer, leading to a kernel crash. This can bring the entire operating system down, causing a denial‑of‑service.

Affected Systems

All Linux kernel implementations released before the commit that changes dev_has_sync_state() to use READ_ONCE() and the corresponding WRITE_ONCE() in device_set_driver() are affected. This includes every distribution kernel version that predates the patch. No specific version range is listed in the CVE data, so a vulnerability assessment should assume that any unpatched kernel is at risk.

Risk and Exploitability

A CVSS score of 7.8 is assigned, and the EPSS score is <1%, indicating a very low probability of exploitation in general. The flaw can be triggered by an attacker with the ability to initiate a race between normal device usage and a device unbind operation, which typically requires local access or device control. Based on the description, it is inferred that the attack vector is local. While the potential for exploitation is high enough to cause a system crash, there is no evidence of remote exploitation or privilege escalation. Consequently, the risk level is moderate to high for environments that allow unbind operations from untrusted contexts. Because the vulnerability is not listed in the CISA KEV catalog, no known wild exploits have been reported.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Roll the Linux kernel to a version that incorporates the patch which uses READ_ONCE() for dev->driver in dev_has_sync_state() and the matching WRITE_ONCE() in device_set_driver().
  • If an immediate kernel update is not possible, restrict or disable hotplug or unbind operations for critical devices while they are in use to eliminate the race window.
  • Enable automatic kernel updates or schedule regular kernel upgrades to ensure the kernel patch is applied without manual intervention.

Generated by OpenCVE AI on August 31, 2026 at 15:56 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-8875-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8877-1 Linux kernel (GCP) vulnerabilities
Ubuntu USN Ubuntu USN USN-8878-1 Linux kernel (GCP) vulnerabilities
Ubuntu USN Ubuntu USN USN-8879-1 Linux kernel (Oracle) vulnerabilities
Ubuntu USN Ubuntu USN USN-8887-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8888-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8889-1 Linux kernel (OEM) vulnerabilities
Ubuntu USN Ubuntu USN USN-8887-2 Linux kernel (AWS) vulnerabilities
Ubuntu USN Ubuntu USN USN-8888-2 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8875-2 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-8887-3 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8917-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8918-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9002-1 Linux kernel (NVIDIA Tegra) vulnerabilities
Ubuntu USN Ubuntu USN USN-9003-1 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-9024-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9025-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9026-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9029-1 Linux kernel (Raspberry Pi) vulnerabilities
Ubuntu USN Ubuntu USN USN-9040-1 Linux kernel (Low Latency NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-9043-1 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-9066-1 Linux kernel (HWE) vulnerabilities
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-416
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}

Type Values Removed Values Added
Weaknesses CWE-416
Type Values Removed Values Added
Weaknesses CWE-362
CWE-416
Type Values Removed Values Added
Weaknesses CWE-362
CWE-416
Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: driver core: use READ_ONCE() for dev->driver in dev_has_sync_state() dev_has_sync_state() reads dev->driver twice without holding device_lock() -- once for the NULL check and once to dereference ->sync_state. Some callers only hold device_links_write_lock, which doesn't prevent a concurrent unbind from clearing dev->driver via device_unbind_cleanup(). Fix it by reading dev->driver exactly once with READ_ONCE(), pairing with the WRITE_ONCE() in device_set_driver().
Title driver core: use READ_ONCE() for dev->driver in dev_has_sync_state()
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 16, 2026, 7:26 PM
Reserved
Aug 26, 2026, 2:34 PM
Status
Received
Published
Aug 28, 2026, 8:16 AM
Modified
Oct 16, 2026, 8:18 PM
Severity
Moderate
Public date
Aug 28, 2026, 12:00 AM