Memory Management Vulnerability in Linux Kernel: Proper Freeing of Crypto Data
Summary
CVE-2025-38575: 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_al... Affects linux versions < 6.1.135-1. Fixed in 6.1.135-1. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The Linux kernel is a core component of the Linux operating system, responsible for managing hardware resources and providing essential services to applications. It is widely used across various distributions, including Debian. The kernel's functionality includes process management, memory management, device drivers, and system calls. This vulnerability specifically affects the ksmbd module, which is responsible for implementing the SMB protocol, allowing file sharing and printing services over a network. The vulnerability arises from improper memory management, which can lead to sensitive data exposure.
Vulnerability Detail
In the Linux kernel, specifically within the ksmbd module, a vulnerability has been identified where the function aead_request_free() is not used to free memory allocated by aead_request_alloc(). Instead, kfree() is used, which does not ensure that sensitive cryptographic data is zeroed before being freed. This oversight can potentially lead to sensitive information being exposed in memory after the allocation has been freed, posing a security risk.
How To Fix
Minimum fixed version
6.1.135-1
This is the first release that contains the fix.
sudo apt-get install --only-upgrade linuxTip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
Currently, there are no specific workarounds provided for this vulnerability. The best course of action is to apply the patch as soon as it becomes available.
Conclusion
The CVE-2025-38575 vulnerability in the Linux kernel highlights the importance of proper memory management, particularly in cryptographic functions. Users are encouraged to update their systems to mitigate the risk of sensitive data exposure. Utilizing tools like Vulert can help in monitoring and addressing such vulnerabilities effectively.
See every vulnerability recorded for linux →
FAQ
CVE-2025-38575 is a vulnerability in the Linux kernel related to improper memory management in the ksmbd module, which can lead to sensitive data exposure.
You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.
While there are no specific workarounds, it is advisable to monitor your system for any suspicious activity and plan to update to the patched version as soon as possible.
If exploited, this vulnerability could lead to the exposure of sensitive cryptographic data, which could be leveraged by attackers for malicious purposes.
No, while the details provided are specific to Debian distributions, the vulnerability exists in the Linux kernel itself and can affect other distributions that utilize the same kernel version.
Related vulnerabilities
Recent vulnerabilities recorded for linux.
