CVE-2026-68351: Linux kernel · wifi: carl9170: bound memcpy length in cmd callback to prevent OOB read
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f74e34e66379e487a09009a4f2d42470051672bd : update Linux kernel when convenient.
Data as of 6 Nov 2026, 17:04 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- 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-11-06.
- Patch
- Available – fixed in f74e34e66379e487a09009a4f2d42470051672bd, cb7a38810cf25738176dac32dec7a146b3f959cf, 525036b20ef01d814a7fcd0567d123992e4479fa +5
Exploitation evidence
Disclosed: evidence found.
CVE published 10 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 6 Nov 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: carl9170: bound memcpy length in cmd callback to prevent OOB read When the firmware sends a command response with a length mismatch, carl9170_cmd_callback() logs the mismatch and calls carl9170_restart() but then falls through to memcpy(ar->readbuf, buffer + 4, len - 4). Since len comes from the firmware and can exceed ar->readlen, this copies more data than the readbuf was allocated for. Bound the memcpy to min(len - 4, ar->readlen) so that the response is still completed -- avoiding repeated restarts from queued garbage -- while preventing an overread past the response buffer.
References
- git.kernel.org/stable/c/38e240996a6a78c94ab07d461fd66e361d55c3c4 (opens in a new tab)
- git.kernel.org/stable/c/2d05c321d27624c413c950278d2dc8e0f44a8950 (opens in a new tab)
- git.kernel.org/stable/c/525036b20ef01d814a7fcd0567d123992e4479fa (opens in a new tab)
- git.kernel.org/stable/c/f74e34e66379e487a09009a4f2d42470051672bd (opens in a new tab)
- git.kernel.org/stable/c/500c36649f270de05a56591fcc1aaaa36687958e (opens in a new tab)
- git.kernel.org/stable/c/9aee949c68dc6dccbc54333537b109c53fe2079f (opens in a new tab)
- git.kernel.org/stable/c/cb7a38810cf25738176dac32dec7a146b3f959cf (opens in a new tab)
- git.kernel.org/stable/c/4cde55b2feff9504d1f993ab80e84e7ccb62791c (opens in a new tab)