driver core: use READ_ONCE() for dev->driver in dev_has_sync_state()
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().
- Published
- Aug 28, 2026
- Updated
- Aug 29, 2026
- EPSS
- 0.2% · 6th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6d88283a49425eb469aa60ffebe76539e73c933e, 5.6affected
- ac338acf514e7b578fa9e3742ec2c292323b4c1a and later · before 89789e4c141904506163dcb91c7289a074573931affected · git
- ac338acf514e7b578fa9e3742ec2c292323b4c1a and later · before 51b3e1de53ee5b7775c7ff90e67fdb2665fce938affected · git
- ac338acf514e7b578fa9e3742ec2c292323b4c1a and later · before 358697929351f619143f59c6a8a15a4994748b79affected · git
- ac338acf514e7b578fa9e3742ec2c292323b4c1a and later · before 5e79e0180515b31b2e2244dc3d256fd8b5a07021affected · git
- ac338acf514e7b578fa9e3742ec2c292323b4c1a and later · before 860885fcd2611bca8c28dac8b2c1c7ff160f763eaffected · git
- ac338acf514e7b578fa9e3742ec2c292323b4c1a and later · before cc77f0d91e3214e4292208f02a1dc09a31f9aac7affected · git
- ac338acf514e7b578fa9e3742ec2c292323b4c1a and later · before 9b0f4082a09760939588135d60a8e9cc994bfa3eaffected · git
- ac338acf514e7b578fa9e3742ec2c292323b4c1a and later · before e9506871a8ea304cde48ff4a57226df2aadddae3affected · git
- 5.5.13 and later · before 5.6affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
- CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 358697929351f619143f59c6a8a15a4994748b79 | Vendor (CNA) |
| Linux Linux | 5.6 | Vendor (CNA) |
| Linux Linux | 51b3e1de53ee5b7775c7ff90e67fdb2665fce938 | Vendor (CNA) |
| Linux Linux | 5e79e0180515b31b2e2244dc3d256fd8b5a07021 | Vendor (CNA) |
| Linux Linux | 860885fcd2611bca8c28dac8b2c1c7ff160f763e | Vendor (CNA) |
| Linux Linux | 89789e4c141904506163dcb91c7289a074573931 | Vendor (CNA) |
| Linux Linux | 9b0f4082a09760939588135d60a8e9cc994bfa3e | Vendor (CNA) |
| Linux Linux | cc77f0d91e3214e4292208f02a1dc09a31f9aac7 | Vendor (CNA) |
| Linux Linux | e9506871a8ea304cde48ff4a57226df2aadddae3 | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- git.kernel.org/stable/c/358697929351f619143f59c6a8a15a4994748b79
- git.kernel.org/stable/c/51b3e1de53ee5b7775c7ff90e67fdb2665fce938
- git.kernel.org/stable/c/5e79e0180515b31b2e2244dc3d256fd8b5a07021
- git.kernel.org/stable/c/860885fcd2611bca8c28dac8b2c1c7ff160f763e
- git.kernel.org/stable/c/89789e4c141904506163dcb91c7289a074573931
- git.kernel.org/stable/c/9b0f4082a09760939588135d60a8e9cc994bfa3e
- git.kernel.org/stable/c/cc77f0d91e3214e4292208f02a1dc09a31f9aac7
- git.kernel.org/stable/c/e9506871a8ea304cde48ff4a57226df2aadddae3
Vendor advisories and official records. Exploit/PoC links are deliberately left out.