Linux kernel USB gadget f_eem eem_unwrap memory leak
CVE-2025-68289 is a memory management flaw in the Linux kernel USB gadget EEM component, specifically in the f_eem driver’s eem_unwrap function. The vulnerable code did not correctly handle the failure case of usb_ep_queue in the command path. When usb_ep_queue failed, previously allocated objects were not freed, resulting in leaked kernel memory. The upstream fix adds error handling to release all allocated resources on usb_ep_queue failure. Reported kmemleak traces show unreferenced allocations originating from skb_clone, usb_ep_alloc_request, and kmalloc paths within eem_unwrap.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Recent activity
4 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.