# CVE-2026-68352: wifi: ath6kl: fix OOB read from firmware IE lengths in connect event

> An out-of-bounds read in the ath6kl Wi-Fi driver allows attackers to read memory or cause state corruption via crafted firmware events.

- **Severity:** High 8.3 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/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-68352, DEBIAN-CVE-2026-68352, GHSA-3chg-p6wm-r59m, UBUNTU-CVE-2026-68352

## What is CVE-2026-68352?

CVE-2026-68352 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 IE lengths in connect event

The firmware-controlled beacon_ie_len, assoc_req_len, and assoc_resp_len
fields in ath6kl_wmi_connect_event_rx() are not validated against the
buffer length. Their sum (up to 765) can exceed the actual WMI event
data, causing out-of-bounds reads during IE parsing and state corruption
of wmi->is_wmm_enabled.

Add a check that the total IE length fits within the buffer.

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

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


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

Apply the vendor's patch.

## Is CVE-2026-68352 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-68352 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-68352 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-68352/ (Markdown: https://insights.sbomify.com/CVE-2026-68352/index.md)
```

## Sources

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

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