CVE-2025-68312
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-12-16

Last updated on: 2025-12-18

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: usbnet: Prevents free active kevent The root cause of this issue are: 1. When probing the usbnet device, executing usbnet_link_change(dev, 0, 0); put the kevent work in global workqueue. However, the kevent has not yet been scheduled when the usbnet device is unregistered. Therefore, executing free_netdev() results in the "free active object (kevent)" error reported here. 2. Another factor is that when calling usbnet_disconnect()->unregister_netdev(), if the usbnet device is up, ndo_stop() is executed to cancel the kevent. However, because the device is not up, ndo_stop() is not executed. The solution to this problem is to cancel the kevent before executing free_netdev().
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-16
Last Modified
2025-12-18
Generated
2026-05-07
AI Q&A
2025-12-16
EPSS Evaluated
2026-05-05
NVD
CVE-2025-68312
EUVD
EUVD-2025-203757
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability occurs in the Linux kernel's usbnet driver. When the usbnet device is probed, a kevent work is scheduled in the global workqueue, but it may not be scheduled before the device is unregistered. If free_netdev() is called while the kevent is still active, it causes a 'free active object (kevent)' error. Additionally, if the device is not up during disconnect, the kevent cancellation function (ndo_stop) is not called, leaving the kevent active. The fix involves cancelling the kevent before calling free_netdev().


How can this vulnerability impact me? :

This vulnerability can lead to a use-after-free or double-free error in the kernel, potentially causing system instability, crashes, or denial of service. It may affect the reliability of the usbnet device driver and could be exploited to disrupt normal device operation.


What immediate steps should I take to mitigate this vulnerability?

The immediate step to mitigate this vulnerability is to ensure that the kevent is cancelled before executing free_netdev() when handling usbnet devices. This involves applying the patch or update that fixes the issue by preventing free active kevent errors during usbnet device unregistration.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart