# CVE-2026-68351: wifi: carl9170: bound memcpy length in cmd callback to prevent OOB read

> A missing bounds check in the carl9170 Wi-Fi driver allows out-of-bounds reads, potentially leaking memory or causing crashes.

- **Severity:** Not scored
- **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 Aug 2026
- **Also known as:** BELL-CVE-2026-68351, DEBIAN-CVE-2026-68351, GHSA-grvp-5p4h-rcmp, UBUNTU-CVE-2026-68351

## What is CVE-2026-68351?

CVE-2026-68351 is a 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: 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.

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


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

Apply the vendor's patch.

## Is CVE-2026-68351 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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