CVE-2025-38575
"KSMbd Crypto Data Exposure"
Description
In the Linux kernel, the following vulnerability has been resolved: ksmbd: use aead_request_free to match aead_request_alloc Use aead_request_free() instead of kfree() to properly free memory allocated by aead_request_alloc(). This ensures sensitive crypto data is zeroed before being freed.
INFO
Published Date :
April 18, 2025, 7:15 a.m.
Last Modified :
April 21, 2025, 2:23 p.m.
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Remotely Exploitable :
No
Impact Score :
Exploitability Score :
Public PoC/Exploit Available at Github
CVE-2025-38575 has a 1 public PoC/Exploit available at Github.
Go to the Public Exploits tab to see the list.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2025-38575.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
DSA and DLA for Debian last 14 days
Python
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2025-38575 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2025-38575 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Apr. 18, 2025
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: ksmbd: use aead_request_free to match aead_request_alloc Use aead_request_free() instead of kfree() to properly free memory allocated by aead_request_alloc(). This ensures sensitive crypto data is zeroed before being freed. Added Reference https://git.kernel.org/stable/c/1de7fec4d3012672e31eeb6679ea60f7ca010ef9 Added Reference https://git.kernel.org/stable/c/3e341dbd5f5a6e5a558e67da80731dc38a7f758c Added Reference https://git.kernel.org/stable/c/46caeae23035192b9cc41872c827f30d0233f16e Added Reference https://git.kernel.org/stable/c/571b342d4688801fc1f6a1934389dac09425dc93 Added Reference https://git.kernel.org/stable/c/6171063e9d046ffa46f51579b2ca4a43caef581a Added Reference https://git.kernel.org/stable/c/a6b594868268c3a7bfaeced912525cd2c445529a Added Reference https://git.kernel.org/stable/c/aef10ccd74512c52e30c5ee19d0031850973e78d
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2025-38575 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2025-38575
weaknesses.