CVE-2026-68351

wifi: carl9170: bound memcpy length in cmd callback to prevent OOB read

N/A
Published: August 10, 2026 at 12:03 PM UTC
Updated: August 19, 2026 at 05:20 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.37 ≤ v < 5.10.2652.6.37 ≤ v < 5.15.2162.6.37 ≤ v < 6.1.1832.6.37 ≤ v < 6.12.1012.6.37 ≤ v < 6.18.422.6.37 ≤ v < 6.6.1482.6.37 ≤ v < 7.1.62.6.37 ≤ v < 7.22.6.37a84fab3cbfdc427e7d366f1cc844f27b2084c26c
Vendor states this is fixed in 2d05c321d27624c413c950278d2dc8e0f44a8950 (fixed)
Vendor states this is fixed in 38e240996a6a78c94ab07d461fd66e361d55c3c4 (fixed)
Vendor states this is fixed in 4cde55b2feff9504d1f993ab80e84e7ccb62791c (fixed)
Vendor states this is fixed in 500c36649f270de05a56591fcc1aaaa36687958e (fixed)
Vendor states this is fixed in 525036b20ef01d814a7fcd0567d123992e4479fa (fixed)
Vendor states this is fixed in 9aee949c68dc6dccbc54333537b109c53fe2079f (fixed)
Vendor states this is fixed in cb7a38810cf25738176dac32dec7a146b3f959cf (fixed)
Vendor states this is fixed in f74e34e66379e487a09009a4f2d42470051672bd (fixed)
Vendor states this is fixed in 2.6.37 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card