# CVE-2026-68349: wifi: carl9170: fix buffer overflow in rx_stream failover path

> A buffer overflow in the carl9170 WiFi driver can cause a kernel panic via crafted USB transfers, leading to denial of service.

- **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-68349, DEBIAN-CVE-2026-68349, GHSA-fpjh-9gv6-cr6g, UBUNTU-CVE-2026-68349

## What is CVE-2026-68349?

CVE-2026-68349 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: fix buffer overflow in rx_stream failover path

The failover continuation in carl9170_rx_stream() copies the full tlen
from the second USB transfer instead of capping at rx_failover_missing
bytes. When both transfers are near maximum size, the total exceeds the
65535-byte failover SKB, triggering skb_over_panic.

Limit the copy size to the missing byte count.

[Fix checkpatch CHECK:PARENTHESIS_ALIGNMENT]

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


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

Apply the vendor's patch.

## Is CVE-2026-68349 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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