# CVE-2026-64242: usb: gadget: net2280: Fix double free in probe error path

> A double free vulnerability in the Linux kernel net2280 USB gadget driver allows attackers to cause denial of service or potentially execute code via a crafted probe error path.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 24 Jul 2026
- **Updated:** 24 Jul 2026
- **Also known as:** BELL-CVE-2026-64242, DEBIAN-CVE-2026-64242, GHSA-6mf3-xx2m-8j4w, ROOT-OS-UBUNTU-2204-CVE-2026-64242, UBUNTU-CVE-2026-64242

## What is CVE-2026-64242?

CVE-2026-64242 is a high-severity use after free vulnerability in Linux kernel, published on 24 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:

usb: gadget: net2280: Fix double free in probe error path

usb_initialize_gadget() installs gadget_release() as the release
callback for the embedded gadget device.  The struct net2280 instance is
therefore released through gadget_release() when the gadget device's last
reference is dropped.

The probe error path calls net2280_remove(), which tears down the
partially initialized device and drops the gadget reference with
usb_put_gadget().  Calling kfree(dev) afterwards can free the same object
again.

Drop the explicit kfree() and let the gadget device release callback
handle the final free.  This issue was found by a static analysis tool
I am developing.

Weakness: CWE-415 (Double Free)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2026-64242 being exploited?

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

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-64242 is a high-severity use after free vulnerability in Linux kernel, published on 24 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-64242 in the wild and no public exploit code.

Affected product: Linux kernel. 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-64242/ (Markdown: https://insights.sbomify.com/CVE-2026-64242/index.md)
```

## Sources

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

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