Linux kernel bridge list corruption in DRM bridge registration
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
In the Linux kernel, drm_bridge_add() can modify a bridge list without holding the lock when re-adding a previously removed bridge. Concurrent bridge operations may corrupt either bridge list; the input does not describe an attacker path or specify network, authentication, or user-interaction requirements.
Engineers running the Linux kernel should check for affected versions; none are specified in the input.