# CVE-2026-74460: can: ems_usb: validate CPC message lengths

> A missing length validation in the Linux kernel ems_usb driver allows a local attacker to cause a denial of service via a malicious USB device.

- **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:** 15 Aug 2026
- **Updated:** 3 Oct 2026
- **Also known as:** AZL-96069, BELL-CVE-2026-74460, DEBIAN-CVE-2026-74460, GHSA-596r-rcx5-45wx, UBUNTU-CVE-2026-74460

## What is CVE-2026-74460?

CVE-2026-74460 is a denial of service vulnerability in Linux, published on 15 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:

can: ems_usb: validate CPC message lengths

ems_usb_read_bulk_callback() walks CPC messages packed in one USB
receive buffer.

Check that each declared message fits in the URB payload. Also require the
type-specific payload to cover the fields used by the CAN, state, error and
overrun handlers.

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


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

Apply the vendor's patch.

## Is CVE-2026-74460 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74460 is a denial of service vulnerability in Linux, published on 15 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-74460 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-74460/ (Markdown: https://insights.sbomify.com/CVE-2026-74460/index.md)
```

## Sources

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

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