net: bcmasp: clear txcb->last before writing each descriptor
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: bcmasp: clear txcb->last before writing each descriptor
bcmasp_xmit() only wrote txcb->last = true for the final fragment of an SKB; non-final fragments left the field untouched. If a descriptor slot was reused while it still held a stale true from a previous SKB (possible when tx_spb_ring_full() underreported fullness), bcmasp_tx_reclaim() would see last == true mid-SKB and call dev_consume_skb_any() prematurely, freeing the sk_buff while its remaining fragments were still in flight.
Unconditionally clear txcb->last before the conditional set so every descriptor slot starts from a known false state regardless of what a prior transmission left behind.
From the CVE record · Linux
The Linux kernel's bcmasp transmit path can retain a stale descriptor flag when a slot is reused. If ring fullness is underreported, reclaim may free an sk_buff while its remaining fragments are still in flight. The input does not specify an attack path, authentication requirements, or user interaction.
Engineers running Linux kernels with the bcmasp driver should check their exposure; affected versions are not specified.