bridge: Fix sleep in atomic context in sysfs 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 sysfs path
Since the start of the git history, brport_store() always acquired the bridge lock. 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 was only used by two STP related attributes (cost and priority).
Nowadays, brport_store() 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's bridge sysfs path holds a bridge lock while changing certain port flags, even though the resulting operation can sleep. A local user able to write the affected bridge port sysfs attributes can trigger a sleeping-in-atomic-context warning; the input does not specify a further impact.
Engineers running Linux kernels with bridge port sysfs support should check their deployments; affected versions are not specified.