Unspecified impact via driver pointer race
Published Aug 28, 2026 · Updated Aug 28, 2026
A race condition in the Linux kernel driver core allows attackers to cause unspecified impact via unspecified vectors. The dev_has_sync_state() function reads dev->driver twice without device_lock(), so device_unbind_cleanup() can clear it between the NULL check and sync_state dereference. Reachability requires a concurrent driver unbind while a caller holds only device_links_write_lock; the Linux CNA record does not state the resulting impact.
Summary
What happened
A race condition in the Linux kernel driver core allows attackers to cause unspecified impact via unspecified vectors. The dev_has_sync_state() function reads dev->driver twice without device_lock(), so device_unbind_cleanup() can clear it between the NULL check and sync_state dereference. Reachability requires a concurrent driver unbind while a caller holds only device_links_write_lock; the Linux CNA record does not state the resulting impact.
The record
- CVE
- CVE-2026-80677
- Published
- Aug 28, 2026
- Updated
- Aug 28, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Aug 28, 2026CVE publishedPublication date reported by the CVE source.
- Aug 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.5.13 <5.6
- Affected versionversion=5.6
- Affected versionversion=6d88283a49425eb469aa60ffebe76539e73c933e
- Affected versionversion=ac338acf514e7b578fa9e3742ec2c292323b4c1a <358697929351f619143f59c6a8a15a4994748b79
- Affected versionversion=ac338acf514e7b578fa9e3742ec2c292323b4c1a <51b3e1de53ee5b7775c7ff90e67fdb2665fce938
- Affected versionversion=ac338acf514e7b578fa9e3742ec2c292323b4c1a <5e79e0180515b31b2e2244dc3d256fd8b5a07021
- Affected versionversion=ac338acf514e7b578fa9e3742ec2c292323b4c1a <860885fcd2611bca8c28dac8b2c1c7ff160f763e
- Affected versionversion=ac338acf514e7b578fa9e3742ec2c292323b4c1a <89789e4c141904506163dcb91c7289a074573931
- Affected versionversion=ac338acf514e7b578fa9e3742ec2c292323b4c1a <9b0f4082a09760939588135d60a8e9cc994bfa3e
- Affected versionversion=ac338acf514e7b578fa9e3742ec2c292323b4c1a <cc77f0d91e3214e4292208f02a1dc09a31f9aac7
- Affected versionversion=ac338acf514e7b578fa9e3742ec2c292323b4c1a <e9506871a8ea304cde48ff4a57226df2aadddae3
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo