Sensitive crypto data retention via mismatched deallocator
Published Apr 18, 2025 · Updated May 11, 2026
Sensitive-data retention in affected Linux ksmbd kernels beginning with 5.15 allows local users to leave crypto request data in freed memory. The free_req path in ksmbd_crypt_message calls kfree() for memory created by aead_request_alloc(), bypassing the request-specific zeroing performed by aead_request_free(). Reaching the path requires low-privileged local access and ksmbd cryptographic message processing; public sources do not demonstrate extraction of the residual data, and NVD records availability impact only.
Summary
What happened
Sensitive-data retention in affected Linux ksmbd kernels beginning with 5.15 allows local users to leave crypto request data in freed memory. The free_req path in ksmbd_crypt_message calls kfree() for memory created by aead_request_alloc(), bypassing the request-specific zeroing performed by aead_request_free(). Reaching the path requires low-privileged local access and ksmbd cryptographic message processing; public sources do not demonstrate extraction of the residual data, and NVD records availability impact only.
The record
- CVE
- CVE-2025-38575
- Published
- Apr 18, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 18, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.15
- Affected versionversion=e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <1de7fec4d3012672e31eeb6679ea60f7ca010ef9
- Affected versionversion=e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <3e341dbd5f5a6e5a558e67da80731dc38a7f758c
- Affected versionversion=e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <46caeae23035192b9cc41872c827f30d0233f16e
- Affected versionversion=e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <571b342d4688801fc1f6a1934389dac09425dc93
- Affected versionversion=e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <6171063e9d046ffa46f51579b2ca4a43caef581a
- Affected versionversion=e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <a6b594868268c3a7bfaeced912525cd2c445529a
- Affected versionversion=e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <aef10ccd74512c52e30c5ee19d0031850973e78d
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo