CVE-2025-68323
BaseFortify
Publication date: 2025-12-18
Last updated on: 2025-12-19
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 use-after-free bug in the Linux kernel's USB Type-C UCSI driver. Specifically, a delayed work item (uec->work) is scheduled but not properly canceled when the device is removed. This leads to scenarios where the driver structures are freed while work related to them is still executing or pending, causing the system to access memory that has already been freed. This can result in memory corruption and system instability.
How can this vulnerability impact me? :
The use-after-free vulnerability can cause memory corruption, which may lead to system crashes, instability, or potentially allow an attacker to execute arbitrary code with kernel privileges. This can compromise the security and reliability of the affected system.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring for use-after-free errors related to the gaokun_ucsi driver in the Linux kernel. Specifically, enabling Kernel Address Sanitizer (KASAN) can help detect such memory errors. You can check kernel logs for KASAN reports indicating slab-use-after-free errors involving gaokun_ucsi. Commands to assist detection include: 1) dmesg | grep -i kasan 2) journalctl -k | grep -i kasan 3) Checking for crashes or warnings related to usb typec or ucsi subsystems in kernel logs. There are no specific network commands as this is a kernel memory issue.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where this vulnerability is fixed, as the issue is resolved by proper cancellation of delayed work in the gaokun_ucsi_remove() function. If updating is not immediately possible, avoid unloading or removing the gaokun_ucsi driver or related USB Type-C components to reduce triggering the use-after-free condition. Monitoring system stability and kernel logs for related errors is also advised.