# CVE-2026-64547: net: usb: net1080: validate packet_len before pad-byte access in rx_fixup

> A malicious USB device can trigger an out-of-bounds read in the Linux kernel net1080 driver, potentially causing a crash or leaking memory.

- **Severity:** High 8.1 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H`)
- **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:** 27 Jul 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-94064, BELL-CVE-2026-64547, DEBIAN-CVE-2026-64547, GHSA-wxqx-m575-fh25, ROOT-OS-DEBIAN-12-CVE-2026-64547, UBUNTU-CVE-2026-64547

## What is CVE-2026-64547?

CVE-2026-64547 is a high-severity memory corruption vulnerability in Linux, published on 27 Jul 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:

net: usb: net1080: validate packet_len before pad-byte access in rx_fixup

For an even packet_len, net1080_rx_fixup() reads the pad byte at
skb->data[packet_len] before the skb->len != packet_len check further
down, and packet_len is only bounded against NC_MAX_PACKET. A malicious
NetChip 1080 device can send a short frame advertising a large even
packet_len (e.g. 0x4000), so the pad-byte read lands past the end of the
skb:

  BUG: KASAN: slab-out-of-bounds in net1080_rx_fixup
  Read of size 1 at addr ffff8880106c83c6 by task ksoftirqd/0/14
   ...
   net1080_rx_fixup (drivers/net/usb/net1080.c:384)
   usbnet_bh (drivers/net/usb/usbnet.c:1589)
   process_one_work (kernel/workqueue.c:3322)
   bh_worker (kernel/workqueue.c:3708)
   tasklet_action (kernel/softirq.c:965)
   handle_softirqs (kernel/softirq.c:622)
   ...

Reject the frame when packet_len >= skb->len before reading.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

Apply the vendor's patch.

## Is CVE-2026-64547 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-64547 is a high-severity memory corruption vulnerability in Linux, published on 27 Jul 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-64547 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-64547/ (Markdown: https://insights.sbomify.com/CVE-2026-64547/index.md)
```

## Sources

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

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