CVE-2026-80677

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-28. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

August 28, 2026

Last Modified

August 29, 2026

Advisory Details (8)

Auto-updated Aug 29, 2026
No patch confirmed yet.
generic

driver core: use READ_ONCE() for dev->driver in dev_has_sync_state() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e9506871a8ea304cde48ff4a57226df2aadddae3
generic

driver core: use READ_ONCE() for dev->driver in dev_has_sync_state() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9b0f4082a09760939588135d60a8e9cc994bfa3e
generic

driver core: use READ_ONCE() for dev->driver in dev_has_sync_state() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cc77f0d91e3214e4292208f02a1dc09a31f9aac7
generic

driver core: use READ_ONCE() for dev->driver in dev_has_sync_state() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/860885fcd2611bca8c28dac8b2c1c7ff160f763e
generic

driver core: use READ_ONCE() for dev->driver in dev_has_sync_state() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5e79e0180515b31b2e2244dc3d256fd8b5a07021
generic

driver core: use READ_ONCE() for dev->driver in dev_has_sync_state() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/358697929351f619143f59c6a8a15a4994748b79
generic

driver core: use READ_ONCE() for dev->driver in dev_has_sync_state() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/51b3e1de53ee5b7775c7ff90e67fdb2665fce938
generic

driver core: use READ_ONCE() for dev->driver in dev_has_sync_state() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/89789e4c141904506163dcb91c7289a074573931

Vendor Advisories for CVE-2026-80677(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 12× in last 7d / 12× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-29 18:45 UTCEG score recompute
  3. 2026-08-29 18:44 UTCGHSA enrichment
  4. 2026-08-29 07:26 UTCEG score recompute
  5. 2026-08-29 07:26 UTCGHSA enrichment
  6. 2026-08-29 06:36 UTCEG score recompute▲ 7.80
  7. 2026-08-29 06:36 UTCGHSA enrichment
  8. 2026-08-29 06:33 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  9. 2026-08-28 21:42 UTCEPSS rescore
  10. 2026-08-28 08:20 UTCNVD update
  11. 2026-08-28 07:34 UTCEG score recompute
  12. 2026-08-28 07:32 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-80677?
CVE-2026-80677 is a high vulnerability published on August 28, 2026. In the Linux kernel, the following vulnerability has been resolved: driver core: use READONCE() for dev->driver in devhassyncstate() devhassync_state() reads dev->driver twice without holding device_lock() -- once for the NULL check and once to dereference ->syncstate. Some callers only hold…
When was CVE-2026-80677 disclosed?
CVE-2026-80677 was first published in the National Vulnerability Database on August 28, 2026, with the most recent update on August 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-80677 actively exploited?
CVE-2026-80677 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.2% of all scored CVEs.
What is the CVSS score of CVE-2026-80677?
CVE-2026-80677 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-80677?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-80677, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-80677

Explore →

Is Your Infrastructure Affected by CVE-2026-80677?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs