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.
Published: 2026-10-18
Score: 5.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Kernel memory corruption
Action: Apply Patch
AI Analysis

Impact

The ath9k_htc Wi‑Fi driver in the Linux kernel aggregates up to 20 frames into a fixed 32 KB buffer without verifying the cumulative size. When large frames of 2,300 bytes are queued, the driver may copy more data than the buffer holds, writing up to 13 KB beyond the allocated buffer. This out‑of‑bounds memcpy corrupts kernel memory, which could be leveraged by an attacker to crash the system, overwrite control data, or potentially gain elevated privileges if they can control the overwritten contents.

Affected Systems

All Linux systems that load the ath9k_htc driver from a kernel that lacks the commit patching the aggregation logic are affected. The flaw is present across the default ath9k_htc driver included in all mainline kernels before the fix, notably on hardware using Qualcomm Atheros wireless adapters.

Risk and Exploitability

The flaw is not listed in the CISA KEV catalog, and the EPSS score indicates a very low exploitation probability (<1%). The likely attack vector is a local user or code that can influence transmitted frames, such as by generating large packets that exceed the MTU or by sending malicious traffic that triggers the driver to aggregate many large frames. Because the memory corruption occurs in kernel space, use of the overflow could lead to a denial of service or, if an attacker can control the overwritten memory, privilege escalation. The risk is high for installations that have not applied the patch, but exploitation would typically require local or privileged access to the driver context.

Generated by OpenCVE AI on October 24, 2026 at 04:25 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply a kernel update that includes the commit patching the TX aggregation logic, such as the release that contains commit 345ce265cf604e84b5b560c21beaf4c6f269ab14.
  • If a kernel update is not yet available, reload the ath9k_htc module or reboot the system to ensure the updated driver code is active.
  • Temporarily mitigate by reducing the MTU on the wireless interface or disabling TX aggregation so that the batch size never exceeds the 32 KB buffer limit as a stopgap measure.

Generated by OpenCVE AI on October 24, 2026 at 04:25 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Debian DLA Debian DLA DLA-4850-1 linux-6.12 security update
History

Sat, 24 Oct 2026 03:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-119

Sat, 24 Oct 2026 00:30:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate


Sun, 18 Oct 2026 22:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-119
CWE-787

Sun, 18 Oct 2026 16:00:00 +0000

Type Values Removed Values Added
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.
Title wifi: ath9k_htc: bound TX aggregation to MAX_TX_BUF_SIZE
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-10-19T09:26:19.987Z

Reserved: 2026-09-25T10:25:14.372Z

Link: CVE-2026-98827

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-18T16:17:36.937

Modified: 2026-10-19T10:19:46.750

Link: CVE-2026-98827

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-10-18T00:00:00Z

Links: CVE-2026-98827 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-10-24T04:30:08Z

Weaknesses