Linux vulnerability

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.

Published 25 Sep 2026Updated 30 Sep 20264 sources
CVSS 7.8

What happened

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.

Affected versions

Linux: 490cb412007de593e07c1d3e2b1ec4233886707c through before 9b26b54861ce05307d39a54ddedddf8747419614 (git); 490cb412007de593e07c1d3e2b1ec4233886707c through before 47a5cecca925ceb175d5adf712e667acf78f475f (git); 490cb412007de593e07c1d3e2b1ec4233886707c through before 17e6ad484dea5ddf1c4a3d6ec77a5929161234de (git); 490cb412007de593e07c1d3e2b1ec4233886707c through before 18e5e0ec0e9282c897e2aa81a3e43ccaee03b003 (git); 6.6 Fixed: See vendor advisory.

Why it matters

Review the vendor advisory and exposure of the affected product to determine operational impact.

Detection & mitigation

  • Apply vendor-provided updates or mitigations.
  • Review affected product exposure and access logs.

Public PoC references

No public PoC reference has passed the current publication threshold.