---
id: "CVE-2026-98973"
kind: "vulnerability"
aliases: ["CVE-2026-98973"]
title: "Linux kernel DRM bridge: unlocked list removal can corrupt bridge lists"
severity: "unknown"
cvss: null
epss: 0.00198
exploited: false
status: "open"
category: "infrastructure"
products: []
ecosystems: []
tags: ["display", "drm", "infrastructure", "linux-kernel"]
not_affected_if: ["unknown"]
published_at: "2026-10-23T13:17:18+00:00"
first_seen_at: "2026-10-23T21:57:33+00:00"
updated_at: "2026-10-25T12:38:50+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98973", "first_seen_at": "2026-10-23T21:57:33+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-98973", "first_seen_at": "2026-10-25T12:38:50+00:00"}]
---

# Linux kernel DRM bridge: unlocked list removal can corrupt bridge lists

In the Linux kernel's DRM bridge code, re-adding a removed bridge drops it from a shared list without holding the lock that protects the list. A race with concurrent bridge removal or the debugfs listing can corrupt the kernel's internal lists.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- unknown

## Fix

- Move to a Linux kernel release that includes the upstream commit 'drm/bridge: Fix unlocked list_del in drm_bridge_add()'; the sources do not name the fixed version.

## Timeline

- 2026-10-23T21:57:33+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-98973
- 2026-10-25T12:38:50+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-98973

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_