# CVE-2025-68289: usb: gadget: f_eem: Fix memory leak in eem_unwrap

> A memory leak in the Linux kernel USB gadget driver allows attackers to cause denial of service by triggering specific USB command paths.

- **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:** 23 May 2026
- **Also known as:** BELL-CVE-2025-68289, DEBIAN-CVE-2025-68289, GHSA-q5w7-j8ph-9r7q, ROOT-OS-DEBIAN-12-CVE-2025-68289, ROOT-OS-DEBIAN-13-CVE-2025-68289, ROOT-OS-UBUNTU-2204-CVE-2025-68289, ROOT-OS-UBUNTU-2404-CVE-2025-68289, UBUNTU-CVE-2025-68289

## What is CVE-2025-68289?

CVE-2025-68289 is a memory corruption 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: f_eem: Fix memory leak in eem_unwrap

The existing code did not handle the failure case of usb_ep_queue in the
command path, potentially leading to memory leaks.

Improve error handling to free all allocated resources on usb_ep_queue
failure. This patch continues to use goto logic for error handling, as the
existing error handling is complex and not easily adaptable to auto-cleanup
helpers.

kmemleak results:
  unreferenced object 0xffffff895a512300 (size 240):
    backtrace:
      slab_post_alloc_hook+0xbc/0x3a4
      kmem_cache_alloc+0x1b4/0x358
      skb_clone+0x90/0xd8
      eem_unwrap+0x1cc/0x36c
  unreferenced object 0xffffff8a157f4000 (size 256):
    backtrace:
      slab_post_alloc_hook+0xbc/0x3a4
      __kmem_cache_alloc_node+0x1b4/0x2dc
      kmalloc_trace+0x48/0x140
      dwc3_gadget_ep_alloc_request+0x58/0x11c
      usb_ep_alloc_request+0x40/0xe4
      eem_unwrap+0x204/0x36c
  unreferenced object 0xffffff8aadbaac00 (size 128):
    backtrace:
      slab_post_alloc_hook+0xbc/0x3a4
      __kmem_cache_alloc_node+0x1b4/0x2dc
      __kmalloc+0x64/0x1a8
      eem_unwrap+0x218/0x36c
  unreferenced object 0xffffff89ccef3500 (size 64):
    backtrace:
      slab_post_alloc_hook+0xbc/0x3a4
      __kmem_cache_alloc_node+0x1b4/0x2dc
      kmalloc_trace+0x48/0x140
      eem_unwrap+0x238/0x36c

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


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

Apply the vendor's patch.

## Is CVE-2025-68289 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-68289 is a memory corruption 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-68289 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-68289/ (Markdown: https://insights.sbomify.com/CVE-2025-68289/index.md)
```

## Sources

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

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