GHSA-JPRM-RCXH-4JGP
Vulnerability from github – Published: 2026-08-28 09:31 – Updated: 2026-08-29 09:30In 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().
{
"affected": [],
"aliases": [
"CVE-2026-80677"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-28T08:16:52Z",
"severity": "HIGH"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndriver core: use READ_ONCE() for dev-\u003edriver in dev_has_sync_state()\n\ndev_has_sync_state() reads dev-\u003edriver twice without holding\ndevice_lock() -- once for the NULL check and once to dereference\n-\u003esync_state. Some callers only hold device_links_write_lock, which\ndoesn\u0027t prevent a concurrent unbind from clearing dev-\u003edriver via\ndevice_unbind_cleanup().\n\nFix it by reading dev-\u003edriver exactly once with READ_ONCE(), pairing\nwith the WRITE_ONCE() in device_set_driver().",
"id": "GHSA-jprm-rcxh-4jgp",
"modified": "2026-08-29T09:30:28Z",
"published": "2026-08-28T09:31:49Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-80677"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/358697929351f619143f59c6a8a15a4994748b79"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/51b3e1de53ee5b7775c7ff90e67fdb2665fce938"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/5e79e0180515b31b2e2244dc3d256fd8b5a07021"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/860885fcd2611bca8c28dac8b2c1c7ff160f763e"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/89789e4c141904506163dcb91c7289a074573931"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/9b0f4082a09760939588135d60a8e9cc994bfa3e"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/cc77f0d91e3214e4292208f02a1dc09a31f9aac7"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/e9506871a8ea304cde48ff4a57226df2aadddae3"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.