CVE-2026-80677

HIGHCVSS 7.8/10EPSS 0.18%

Last modified

CVE-2026-80677 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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().. EPSS estimates a 0.18% chance of exploitation in the next 30 days.

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

Metrics

EPSS Probability
0.18%

7.2th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= ac338acf514e7b578fa9e3742ec2c292323b4c1a, < 89789e4c141904506163dcb91c7289a074573931; >= ac338acf514e7b578fa9e3742ec2c292323b4c1a, < 51b3e1de53ee5b7775c7ff90e67fdb2665fce938; >= ac338acf514e7b578fa9e3742ec2c292323b4c1a, < 358697929351f619143f59c6a8a15a4994748b79; >= ac338acf514e7b578fa9e3742ec2c292323b4c1a, < 5e79e0180515b31b2e2244dc3d256fd8b5a07021; >= ac338acf514e7b578fa9e3742ec2c292323b4c1a, < 860885fcd2611bca8c28dac8b2c1c7ff160f763e; >= ac338acf514e7b578fa9e3742ec2c292323b4c1a, < cc77f0d91e3214e4292208f02a1dc09a31f9aac7; >= ac338acf514e7b578fa9e3742ec2c292323b4c1a, < 9b0f4082a09760939588135d60a8e9cc994bfa3e; >= ac338acf514e7b578fa9e3742ec2c292323b4c1a, < e9506871a8ea304cde48ff4a57226df2aadddae3; 6d88283a49425eb469aa60ffebe76539e73c933e; >= 5.5.13, < 5.6
LinuxLinux5.6

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-80677?
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().
How severe is CVE-2026-80677?
CVE-2026-80677 has a CVSS score of 7.8/10 (HIGH severity). The EPSS model estimates a 0.18% probability of exploitation in the next 30 days.
How do I fix CVE-2026-80677?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-80677?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST