CVE-2025-68289
BaseFortify
Publication date: 2025-12-16
Last updated on: 2025-12-18
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a memory leak in the Linux kernel's USB gadget function f_eem, specifically in the eem_unwrap function. The existing code did not properly handle failures of the usb_ep_queue command, which could lead to allocated memory not being freed. The patch fixes this by improving error handling to ensure all allocated resources are freed when usb_ep_queue fails.
How can this vulnerability impact me? :
The vulnerability can lead to memory leaks in the Linux kernel when the usb_ep_queue command fails in the f_eem USB gadget function. Over time, this could cause increased memory usage and potentially degrade system performance or stability.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring for memory leaks related to the usb: gadget: f_eem driver, specifically looking for unreferenced objects allocated in the eem_unwrap function. Using the Linux kernel's kmemleak tool can help identify such memory leaks. Commands to enable and check kmemleak include: 1. Enable kmemleak (if not already enabled): echo scan > /sys/kernel/debug/kmemleak 2. Check for memory leaks: cat /sys/kernel/debug/kmemleak Look for unreferenced objects with backtraces involving eem_unwrap or usb_ep_queue failures.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where the usb: gadget: f_eem memory leak issue in eem_unwrap has been fixed. The patch improves error handling to free all allocated resources on usb_ep_queue failure, preventing memory leaks. Until the update is applied, monitoring for memory leaks using kmemleak and minimizing use of the affected usb gadget functionality may reduce impact.