CVE-2026-68352: Linux kernel · Out-of-bounds Read
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 8.3 High · fixed in d70c0a850c21b57a6f46ce363860203389bbeaa6 : patch Linux kernel soon.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-10-16.
- Patch
- Available – fixed in d70c0a850c21b57a6f46ce363860203389bbeaa6, a38d7d6376b295245b53bc98b7ca682c027abaf7, 94e1bfcefe8264a207c2fda2febb954e70a34b42 +5
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
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.
References
- git.kernel.org/stable/c/7cae33e3e09a080db96e3a8980c2c8d288318320 (opens in a new tab)
- git.kernel.org/stable/c/1eeed9efc9a40e0635e910c37fee86543041b4e1 (opens in a new tab)
- git.kernel.org/stable/c/a38d7d6376b295245b53bc98b7ca682c027abaf7 (opens in a new tab)
- git.kernel.org/stable/c/1c690f7c4c5b37108ac8c98b94ce1b3c655a4f5e (opens in a new tab)
- git.kernel.org/stable/c/d70c0a850c21b57a6f46ce363860203389bbeaa6 (opens in a new tab)
- git.kernel.org/stable/c/33b5342d2080657054ddf89ef1199b426a37dae8 (opens in a new tab)
- git.kernel.org/stable/c/94e1bfcefe8264a207c2fda2febb954e70a34b42 (opens in a new tab)
- git.kernel.org/stable/c/6b47b29730de3232b919d8362749f6814c5f2a33 (opens in a new tab)