# CVE-2026-68353: wifi: ath6kl: fix OOB read from firmware num_msg in TX complete handler

> A malicious firmware can trigger an out-of-bounds read in the ath6kl Wi-Fi driver, potentially leaking kernel memory or causing a crash.

- **Severity:** High 8.1 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Aug 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-68353, DEBIAN-CVE-2026-68353, GHSA-2244-8pcv-8jr6, UBUNTU-CVE-2026-68353

## What is CVE-2026-68353?

CVE-2026-68353 is a high-severity memory corruption vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

wifi: ath6kl: fix OOB read from firmware num_msg in TX complete handler

The firmware-controlled num_msg field (u8, 0-255) drives the loop in
ath6kl_wmi_tx_complete_event_rx() without validation against the buffer
length. This allows out-of-bounds reads of up to 1020 bytes past the
WMI event buffer when the firmware sends an inflated num_msg.

Add a check that the buffer is large enough to hold the fixed struct
and the num_msg variable-length entries.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-68353?


## How do I fix CVE-2026-68353?

Apply the vendor's patch.

## Is CVE-2026-68353 being exploited?

There is no known exploitation of CVE-2026-68353 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-68353 and fix it if it is affected.

What it is: CVE-2026-68353 is a high-severity memory corruption vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-68353 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-68353/ (Markdown: https://insights.sbomify.com/CVE-2026-68353/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-68353
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-68353
- OSV: https://osv.dev/vulnerability/CVE-2026-68353

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-68353/
Summaries are generated and may contain mistakes; the official description above is the record.