CVE-2025-68263
BaseFortify
Publication date: 2025-12-16
Last updated on: 2026-04-02
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| 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 ksmbd component, specifically in the ipc_msg_send_request() function. The function waits for a generic netlink reply using an ipc_msg_table_entry on the stack. The problem occurs because ipc_msg_send_request() validates and frees the response pointer without holding the same lock that the generic netlink handler uses to fill the response. Under high concurrency, this causes a race condition where the response data is being copied while it has just been freed, leading to a use-after-free error detected by KASAN.
How can this vulnerability impact me? :
This vulnerability can lead to a use-after-free condition in the kernel, which may cause system instability, crashes, or potentially allow an attacker to execute arbitrary code or escalate privileges by exploiting the race condition in the ksmbd component.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where the ksmbd ipc use-after-free vulnerability is fixed. The fix includes proper locking (ipc_msg_table_lock) in ipc_msg_send_request() to prevent the race condition causing the use-after-free. Until an update is applied, limiting or avoiding high concurrency usage of ksmbd IPC may reduce the risk, but the primary step is to apply the patch or kernel update that addresses this issue.