CVE-2026-98827

wifi: ath9k_htc: bound TX aggregation to MAX_TX_BUF_SIZE

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.

Key facts

Published
18 Oct 2026
Last changed
19 Oct 2026
Assigned by
Linux
EPSS
0.2% likely to be exploited in the next 30 days, higher than 9.895% of CVEs (scores for 18 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • fb9987d0f748c983bb795a86f47522313f701a08 up to but excluding c18882768a0fe253c70986c5fe66d9241570fbc4 (affected)
  • fb9987d0f748c983bb795a86f47522313f701a08 up to but excluding 345ce265cf604e84b5b560c21beaf4c6f269ab14 (affected)
  • fb9987d0f748c983bb795a86f47522313f701a08 up to but excluding e73a619f91b6cfec47bc1a94aea28df6849e5be3 (affected)
  • fb9987d0f748c983bb795a86f47522313f701a08 up to but excluding aeaca27c1db3106967ffbb2b517d98c835f6d500 (affected)
LinuxLinux
  • Default status: affected
  • 2.6.35 (affected)
  • 0 up to but excluding 2.6.35 (unaffected)
  • 6.12.113 up to and including 6.12.* (unaffected)
  • 6.18.56 up to and including 6.18.* (unaffected)
  • 7.2.10 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 18 Oct 2026 Published

References