# CVE-2026-68369: usb: gadget: printer: fix infinite loop in printer_read()

> A local attacker can cause an infinite loop in the Linux kernel USB printer gadget driver by triggering a copy_to_user failure, leading to denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **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-68369, DEBIAN-CVE-2026-68369, GHSA-6mcx-v8qc-xx8r, UBUNTU-CVE-2026-68369

## What is CVE-2026-68369?

CVE-2026-68369 is a denial of service 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:

usb: gadget: printer: fix infinite loop in printer_read()

printer_read() uses the same variable for the requested copy size and
the number of bytes actually copied to user space. copy_to_user()
returns the number of bytes not copied, so when it fails to copy
anything, the computed copied length becomes zero.

In that case len, buf, current_rx_bytes and current_rx_buf are left
unchanged. If RX data is available and the user buffer remains
unwritable, the read loop can repeat indefinitely.

Track the copied length separately and return -EFAULT, or the number of
bytes already copied, if an iteration makes no progress.

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


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

Apply the vendor's patch.

## Is CVE-2026-68369 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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