net: bridge: vlan: fix memory leak in __allowed_ingress
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: bridge: vlan: fix memory leak in __allowed_ingress
When using per-vlan state, if vlan snooping and stats are disabled, untagged or priority-tagged ingress frame will go to check pvid state. If the port state is forwarding and the pvid state is not learning/forwarding, untagged or priority-tagged frame will be dropped but skb memory is not freed. Should free skb when __allowed_ingress returns false.
From the CVE record · Linux
The Linux kernel bridge VLAN ingress path can leak packet memory when per-VLAN state is in use and VLAN snooping and stats are disabled. Untagged or priority-tagged ingress frames trigger the leak if the port is forwarding but the PVID state is neither learning nor forwarding.
Operators running Linux kernels with bridge per-VLAN state should check their versions against the vendor advisory.