drm/bridge: Fix unlocked list_del in drm_bridge_add()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 7.2.11
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original 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.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Linux Linux
From 17805a15d1751f5d6bb06f924f9bed216feb8db7 · fixed in f469d850854101eae60dd4080244f114a9bcf2b5; From 17805a15d1751f5d6bb06f924f9bed216feb8db7 · fixed in b62e3db8cdc1680e1c3390591e872f485148541a
- Linux Linux
6.19
- KernelLinux
From 6.19.0 · fixed in 7.2.11