net: dsa: Avoid cross-chip syncing of VLAN filtering
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:
net: dsa: Avoid cross-chip syncing of VLAN filtering
Changes to VLAN filtering are not applicable to cross-chip notifications.
On a system like this:
.-----. .-----. .-----. | sw1 +---+ sw2 +---+ sw3 | '-1-2-' '-1-2-' '-1-2-'
Before this change, upon sw1p1 leaving a bridge, a call to dsa_port_vlan_filtering would also be made to sw2p1 and sw3p1.
In this scenario:
.---------. .-----. .-----. | sw1 +---+ sw2 +---+ sw3 | '-1-2-3-4-' '-1-2-' '-1-2-'
From the CVE record · Linux
The Linux kernel’s DSA VLAN filtering code can send cross-chip notifications for ports that do not exist on other switches. When a bridge port leaves in a multi-chip switch setup, this can cause an out-of-bounds array access and crash on mv88e6xxx. The input does not specify whether an attacker can trigger this remotely or whether authentication or user interaction is required.
Engineers running Linux systems with multi-chip DSA switch setups, particularly mv88e6xxx; affected versions are not specified.