GHSA-69CP-RCR3-V67W
Vulnerability from github – Published: 2026-10-23 15:31 – Updated: 2026-10-23 15:31In the Linux kernel, the following vulnerability has been resolved:
drm/bridge: Fix unlocked list_del in drm_bridge_add()
When re-adding a bridge that was previously removed, drm_bridge_add() drops it from bridge_lingering_list without holding bridge_lock.
Both bridge_list and bridge_lingering_list are protected by bridge_lock, as they are concurrently modified by drm_bridge_remove() and __drm_bridge_free(), and walked by the debugfs 'bridges' file. Running the list_empty() test and the list_del_init() outside of the lock may therefore corrupt either list.
Perform both under bridge_lock.
{
"affected": [],
"aliases": [
"CVE-2026-98973"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-23T13:17:18Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/bridge: Fix unlocked list_del in drm_bridge_add()\n\nWhen re-adding a bridge that was previously removed, drm_bridge_add()\ndrops it from bridge_lingering_list without holding bridge_lock.\n\nBoth bridge_list and bridge_lingering_list are protected by bridge_lock,\nas they are concurrently modified by drm_bridge_remove() and\n__drm_bridge_free(), and walked by the debugfs \u0027bridges\u0027 file. Running\nthe list_empty() test and the list_del_init() outside of the lock may\ntherefore corrupt either list.\n\nPerform both under bridge_lock.",
"id": "GHSA-69cp-rcr3-v67w",
"modified": "2026-10-23T15:31:33Z",
"published": "2026-10-23T15:31:33Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98973"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/b62e3db8cdc1680e1c3390591e872f485148541a"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f469d850854101eae60dd4080244f114a9bcf2b5"
}
],
"schema_version": "1.4.0",
"severity": []
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
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.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
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.