# CVE-2025-68282: usb: gadget: udc: fix use-after-free in usb_gadget_state_work

> A race condition in the Linux kernel USB gadget driver allows local attackers to trigger a use-after-free, potentially leading to code execution or system crashes.

- **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:** 16 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** AZL-72568, BELL-CVE-2025-68282, DEBIAN-CVE-2025-68282, GHSA-8p7c-4hwq-mwgw, ROOT-OS-DEBIAN-11-CVE-2025-68282, ROOT-OS-DEBIAN-12-CVE-2025-68282, ROOT-OS-DEBIAN-13-CVE-2025-68282, ROOT-OS-UBUNTU-2204-CVE-2025-68282, ROOT-OS-UBUNTU-2404-CVE-2025-68282, UBUNTU-CVE-2025-68282

## What is CVE-2025-68282?

CVE-2025-68282 is an use after free vulnerability in Linux, published on 16 Dec 2025. 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: udc: fix use-after-free in usb_gadget_state_work

A race condition during gadget teardown can lead to a use-after-free
in usb_gadget_state_work(), as reported by KASAN:

  BUG: KASAN: invalid-access in sysfs_notify+0x2c/0xd0
  Workqueue: events usb_gadget_state_work

The fundamental race occurs because a concurrent event (e.g., an
interrupt) can call usb_gadget_set_state() and schedule gadget->work
at any time during the cleanup process in usb_del_gadget().

Commit 399a45e5237c ("usb: gadget: core: flush gadget workqueue after
device removal") attempted to fix this by moving flush_work() to after
device_del(). However, this does not fully solve the race, as a new
work item can still be scheduled *after* flush_work() completes but
before the gadget's memory is freed, leading to the same use-after-free.

This patch fixes the race condition robustly by introducing a 'teardown'
flag and a 'state_lock' spinlock to the usb_gadget struct. The flag is
set during cleanup in usb_del_gadget() *before* calling flush_work() to
prevent any new work from being scheduled once cleanup has commenced.
The scheduling site, usb_gadget_set_state(), now checks this flag under
the lock before queueing the work, thus safely closing the race window.

## Which versions are affected by CVE-2025-68282?


## How do I fix CVE-2025-68282?

Apply the vendor's patch.

## Is CVE-2025-68282 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68282 and fix it if it is affected.

What it is: CVE-2025-68282 is an use after free vulnerability in Linux, published on 16 Dec 2025. 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-2025-68282 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-2025-68282/ (Markdown: https://insights.sbomify.com/CVE-2025-68282/index.md)
```

## Sources

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

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