bridge: Fix sleep in atomic context in netlink path
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 |
|
|
6.18.357.0.127.1In the Linux kernel, the following vulnerability has been resolved:
bridge: Fix sleep in atomic context in netlink path
Since the introduction of the netlink configuration path for bridge ports in commit 25c71c75ac87 ("bridge: bridge port parameters over netlink"), br_setport() was always called with the bridge lock held around it. Back then this decision made sense: The bridge lock protects the STP state of the bridge and its ports and at that time the function only processed three STP related netlink attributes (cost, priority and state).
Nowadays, br_setport() processes a lot more attributes and most of them do not need the bridge lock:
* Bridge flags: Only require RTNL. Read locklessly by the data path. Annotations can be added in net-next.
* FDB port flushing: Only requires the FDB lock.
* Multicast attributes: Only require the multicast lock.
* Group forward mask: Only requires RTNL. Read locklessly by the data path. Annotations can be added in net-next.
From the CVE record · Linux
The Linux kernel bridge netlink path can call a function that sleeps while holding the bridge lock. This can trigger a kernel warning when bridge port flags change through netlink; the input does not specify authentication requirements or whether user interaction is needed.
Engineers running Linux kernels that configure bridge ports through netlink should check their exposure; affected versions are not specified.