8021q: delete cleared egress QoS mappings
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:
8021q: delete cleared egress QoS mappings
vlan_dev_set_egress_priority() currently keeps cleared egress priority mappings in the hash as tombstones. Repeated set/clear cycles with distinct skb priorities therefore accumulate mapping nodes until device teardown and leak memory.
Delete mappings when vlan_prio is cleared instead of keeping tombstones. Now that the egress mapping lists are RCU protected, the node can be unlinked safely and freed after a grace period.
From the CVE record · Linux
The Linux kernel's 8021q code retains cleared egress priority mappings instead of deleting them. Repeated set-and-clear cycles with distinct skb priorities can accumulate mapping nodes and leak memory until device teardown. The input does not specify whether exploiting this requires network access, authentication, or user interaction.
Engineers running Linux kernels with 8021q egress QoS mappings should check their systems; affected versions are not specified.