CVE-2025-68817
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2026-01-13

Last updated on: 2026-02-26

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free in ksmbd_tree_connect_put under concurrency Under high concurrency, A tree-connection object (tcon) is freed on a disconnect path while another path still holds a reference and later executes *_put()/write on it.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-01-13
Last Modified
2026-02-26
Generated
2026-05-07
AI Q&A
2026-01-14
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 9 associated CPEs
Vendor Product Version / Range
linux linux_kernel 6.6
linux linux_kernel 6.6
linux linux_kernel 6.6
linux linux_kernel 6.6
linux linux_kernel From 6.7 (inc) to 6.12.64 (exc)
linux linux_kernel From 6.13 (inc) to 6.18.3 (exc)
linux linux_kernel From 5.15.145 (inc) to 5.15.199 (exc)
linux linux_kernel From 6.1.71 (inc) to 6.1.160 (exc)
linux linux_kernel From 6.6.1 (inc) to 6.6.120 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-416 The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability is a use-after-free issue in the Linux kernel's ksmbd component. Specifically, under high concurrency, a tree-connection object (tcon) can be freed on a disconnect path while another path still holds a reference to it and later attempts to use or write to it, leading to potential memory corruption or crashes.


How can this vulnerability impact me? :

The vulnerability can lead to memory corruption or system crashes due to use-after-free conditions when multiple concurrent operations access the same tree-connection object improperly. This can affect system stability and potentially be exploited to cause denial of service or other unintended behavior.


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