Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-80677driver core: use READ_ONCE() for dev->driver in dev_has_sync_state()

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

Timeline

  1. ID reserved

    By Linux

  2. · 2 days later

    Published

  3. · 49 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-80677, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (14 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected ac338acf514e7b578fa9e3742ec2c292323b4c1a – < 89789e4c141904506163dcb91c7289a074573931
    • affected ac338acf514e7b578fa9e3742ec2c292323b4c1a – < 51b3e1de53ee5b7775c7ff90e67fdb2665fce938
    • affected ac338acf514e7b578fa9e3742ec2c292323b4c1a – < 358697929351f619143f59c6a8a15a4994748b79
    • affected ac338acf514e7b578fa9e3742ec2c292323b4c1a – < 5e79e0180515b31b2e2244dc3d256fd8b5a07021
    • affected ac338acf514e7b578fa9e3742ec2c292323b4c1a – < 860885fcd2611bca8c28dac8b2c1c7ff160f763e
    • affected ac338acf514e7b578fa9e3742ec2c292323b4c1a – < cc77f0d91e3214e4292208f02a1dc09a31f9aac7
    • affected ac338acf514e7b578fa9e3742ec2c292323b4c1a – < 9b0f4082a09760939588135d60a8e9cc994bfa3e
    • affected ac338acf514e7b578fa9e3742ec2c292323b4c1a – < e9506871a8ea304cde48ff4a57226df2aadddae3
    • affected 6d88283a49425eb469aa60ffebe76539e73c933e
    • affected 5.5.13 – < 5.6
  • Linux · Linux

    • affected 5.6
    • unaffected < 5.6
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-80677 badge
[![CVE-2026-80677](https://cveledger.app/badge/CVE-2026-80677.svg)](https://cveledger.app/cve/CVE-2026-80677)

Record last updated .