# CVE-2026-98973: drm/bridge: Fix unlocked list_del in drm_bridge_add()


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-98973, GHSA-69cp-rcr3-v67w, UBUNTU-CVE-2026-98973

## What is CVE-2026-98973?

CVE-2026-98973 is a vulnerability in Linux, published on 23 Oct 2026. 

### Official description

In 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.

## Which versions are affected by CVE-2026-98973?


## How do I fix CVE-2026-98973?

Upgrade to a fixed version.

## Is CVE-2026-98973 being exploited?

There is no known exploitation of CVE-2026-98973 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98973 and fix it if it is affected.

What it is: CVE-2026-98973 is a vulnerability in Linux, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-98973 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98973/ (Markdown: https://insights.sbomify.com/CVE-2026-98973/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98973
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98973
- OSV: https://osv.dev/vulnerability/CVE-2026-98973

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98973/
Summaries are generated and may contain mistakes; the official description above is the record.