CyberSecBulletin
CVE-2026-68199NVD status: Received

In the Linux kernel, the following vulnerability has been resolved: wifi: ath6kl: fix OOB…

Published Updated By the CyberSecBulletin desk

CVE-2026-68199 is a high-severity improper input validation vulnerability in Linux, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited from the same local network by an unauthenticated attacker, without any action from a user. The record lists versions c8e3ca7954d8233fbc54bd370c1827670f43c538, f480d9910fcfe326db3a6281df80e83af347193e, 67bc9af4f41f2bdba20404fbd753b2a1bd6dd352 as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.38% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Linux to c8e3ca7954d8233fbc54bd370c1827670f43c538 or f480d9910fcfe326db3a6281df80e83af347193e or 67bc9af4f41f2bdba20404fbd753b2a1bd6dd352 or d4558c140782180e2c80a7588a4af9f8675adfc4, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxbdcd81707973cf8aa9305337166f8ee842a050d4 up to, but not including, c8e3ca7954d8233fbc54bd370c1827670f43c538; bdcd81707973cf8aa9305337166f8ee842a050d4 up to, but not including, f480d9910fcfe326db3a6281df80e83af347193e; bdcd81707973cf8aa9305337166f8ee842a050d4 up to, but not including, 67bc9af4f41f2bdba20404fbd753b2a1bd6dd352; bdcd81707973cf8aa9305337166f8ee842a050d4 up to, but not including, d4558c140782180e2c80a7588a4af9f8675adfc4; bdcd81707973cf8aa9305337166f8ee842a050d4 up to, but not including, 5a65fd4722416061698b0a3277222381efbc4882; bdcd81707973cf8aa9305337166f8ee842a050d4 up to, but not including, 58c6c8dc2e022e1b4f3dc58725a1ca49ff470f9c; bdcd81707973cf8aa9305337166f8ee842a050d4 up to, but not including, cec0a487cf38ac1f9bca240ffe8a94c5014b72f2; bdcd81707973cf8aa9305337166f8ee842a050d4 up to, but not including, 44126b6994eeb28f2103b638e698f40a1244f327; and 1 more rangesc8e3ca7954d8233fbc54bd370c1827670f43c538, f480d9910fcfe326db3a6281df80e83af347193e, 67bc9af4f41f2bdba20404fbd753b2a1bd6dd352, d4558c140782180e2c80a7588a4af9f8675adfc4, 5a65fd4722416061698b0a3277222381efbc4882, 58c6c8dc2e022e1b4f3dc58725a1ca49ff470f9c

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
AdjacentThe attacker must be on the same local network segment.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CNA.

Official description

In the Linux kernel, the following vulnerability has been resolved: wifi: ath6kl: fix OOB access from firmware ADDBA window size aggr_recv_addba_req_evt() logs a debug message when the firmware-supplied win_sz is outside [AGGR_WIN_SZ_MIN, AGGR_WIN_SZ_MAX] but does not return. The out-of-range win_sz is then used in TID_WINDOW_SZ() to compute a kzalloc size and stored in rxtid->hold_q_sz, leading to zero-size or overflowed allocations and subsequent out-of-bounds access. Clean up any previously active aggregation session for the TID first, then return early when win_sz is out of the valid range, instead of proceeding with a broken allocation size.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Input Validation

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How developers prevent this class of flaw

  • Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build recognizers for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of allowing parser code to be scattered throughout the program, where it could be subject to errors or inconsistencies that create weaknesses.
  • Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
  • Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.

More Improper Input Validation vulnerabilities (CWE-20)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Improper Input Validation vulnerabilities

Spotted an error? Tell us.