In the Linux kernel, the following vulnerability has been resolved:
smb: client: fix use-after-free in crypt_message when using async crypto
The CVE-2024-50047 fix removed asynchronous crypto handling from
crypt_message(), assuming all crypto operations are synchronous.
However, when hardware crypto accelerators are used, this can cause
use-after-free crashes:
crypt_message()
// Allocate the creq buffer containing the req
creq = smb2_get_aead_req(..., &req);
// Async encryption returns -EINPROGRESS immediately
rc = enc ? crypto_aead_encrypt(req) : crypto_aead_decrypt(req);
// Free creq while async operation is still in progress
kvfree_sensitive(creq, ...);
Hardware crypto modules often implement async AEAD operations for
performance. When crypto_aead_encrypt/decrypt() returns -EINPROGRESS,
the operation completes asynchronously. Without crypto_wait_req(),
the function immediately frees the request buffer, leading to crashes
when the driver later accesses the freed memory.
This results in a use-after-free condition when the hardware crypto
driver later accesses the freed request structure, leading to kernel
crashes with NULL pointer dereferences.
The issue occurs because crypto_alloc_aead() with mask=0 doesn't
guarantee synchronous operation. Even without CRYPTO_ALG_ASYNC in
the mask, async implementations can be selected.
Fix by restoring the async crypto handling:
- DECLARE_CRYPTO_WAIT(wait) for completion tracking
- aead_request_set_callback() for async completion notification
- crypto_wait_req() to wait for operation completion
This ensures the request buffer isn't freed until the crypto operation
completes, whether synchronous or asynchronous, while preserving the
CVE-2024-50047 fix.
References
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
History
07 Jan 2026, 16:26
| Type | Values Removed | Values Added |
|---|---|---|
| References | () https://git.kernel.org/stable/c/15a0a5de49507062bc3be4014a403d8cea5533de - Patch | |
| References | () https://git.kernel.org/stable/c/2a76bc2b24ed889a689fb1c9015307bf16aafb5b - Patch | |
| References | () https://git.kernel.org/stable/c/5d047b12f86cc3b9fde1171c02d9bccf4dba0632 - Patch | |
| References | () https://git.kernel.org/stable/c/6550b2bef095d0dd2d2c8390d2ea4c3837028833 - Patch | |
| References | () https://git.kernel.org/stable/c/8ac90f6824fc44d2e55a82503ddfc95defb19ae0 - Patch | |
| References | () https://git.kernel.org/stable/c/9a1d3e8d40f151c2d5a5f40c410e6e433f62f438 - Patch | |
| References | () https://git.kernel.org/stable/c/b220bed63330c0e1733dc06ea8e75d5b9962b6b6 - Patch | |
| References | () https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html - Third Party Advisory | |
| References | () https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html - Third Party Advisory | |
| CVSS |
v2 : v3 : |
v2 : unknown
v3 : 7.8 |
| CWE | CWE-416 | |
| CPE | cpe:2.3:o:linux:linux_kernel:6.16:rc6:*:*:*:*:*:* cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:6.16:rc3:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:6.16:rc5:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:6.16:rc4:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:6.16:rc1:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:6.16:rc2:*:*:*:*:*:* |
|
| First Time |
Linux
Debian Debian debian Linux Linux linux Kernel |
03 Nov 2025, 18:16
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
28 Aug 2025, 15:15
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
29 Jul 2025, 14:14
| Type | Values Removed | Values Added |
|---|---|---|
| Summary |
|
28 Jul 2025, 12:15
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2025-07-28 12:15
Updated : 2026-01-07 16:26
NVD link : CVE-2025-38488
Mitre link : CVE-2025-38488
CVE.ORG link : CVE-2025-38488
JSON object : View
Products Affected
debian
- debian_linux
linux
- linux_kernel
CWE
CWE-416
Use After Free
