net: bridge: stop fast-leave after deleting a port group
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 6db6f0eae6052b70885562e1733896647ec1d807 · < 0309ebbc570000ea0df11c06b69798e5860c5f6f| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: bridge: stop fast-leave after deleting a port group
br_multicast_leave_group() iterates mp->ports with pp = &p->next in its fast-leave path. After br_multicast_del_pg() removes p, continuing the loop advances pp through the deleted entry.
If multicast-to-unicast was enabled, the bridge can hold multiple port groups for the same port and group with different source MAC addresses. Once multicast-to-unicast is disabled, br_port_group_equal() matches those entries by port only. A fast leave can then delete one entry and continue from its stale next pointer, leaving mp->ports pointing at a deleted port group.
Fast leave only needs to remove one matching port group. Break after br_multicast_del_pg() so the loop stops before dereferencing the removed entry.
From the CVE record · Linux
The Linux kernel bridge multicast fast-leave path can leave a port-group list pointing at a deleted entry. This can occur when multicast-to-unicast is enabled and then disabled before a fast leave; the input does not establish what an attacker can do or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with bridge multicast should check their exposure; affected versions are not specified.