Linux kernel memory leak in team broadcast transmission
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: team: free skb when broadcast has no txable port
bc_transmit() sends the original skb through the last txable port. When no port is txable, it returns false without consuming the skb, but team_xmit() still returns NETDEV_TX_OK. AF_PACKET sends then retain the skb and its socket write-memory charge.
A TX-enabled, link-down port keeps the broadcast transmit op installed. Carrier can stay up through a second link-up, TX-disabled port or be forced on by userspace. Free the original skb on the no-port path while leaving the existing drop accounting intact.
Discovered by Sashiko during review of previous commit.
From the CVE record · Linux
The Linux kernel’s team network driver can retain a packet buffer and its socket write-memory charge when a broadcast send has no transmit-capable port. This can occur with a TX-enabled, link-down port while carrier remains up or is forced on by userspace. The issue is triggered by a local AF_PACKET send; the input does not specify authentication or other user-interaction requirements.
Operators running Linux kernels with the team network driver should check whether their kernel is affected; no affected versions are specified.