Skip to content
CVE PROGRAM SOURCE RECORD9.8 Critical

CVE-2025-38488

smb: client: fix use-after-free in crypt_message when using async crypto

Read JSON ↗CVE.org ↗
Status
Published
Published
Updated
Assigning organization
Linux

Description

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.

Affected products

Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.

Linux Linux

Default version status: unaffected

  • 8f14a476abba13144df5434871a7225fd29af633 to < 5d047b12f86cc3b9fde1171c02d9bccf4dba0632affected
  • ef51c0d544b1518b35364480317ab6d3468f205d to < 6550b2bef095d0dd2d2c8390d2ea4c3837028833affected
  • bce966530fd5542bbb422cb45ecb775f7a1a6bc3 to < 9a1d3e8d40f151c2d5a5f40c410e6e433f62f438affected
  • 0809fb86ad13b29e1d6d491364fc7ea4fb545995 to < 15a0a5de49507062bc3be4014a403d8cea5533deaffected
  • b0abcd65ec545701b8793e12bc27dc98042b151a to < 2a76bc2b24ed889a689fb1c9015307bf16aafb5baffected
  • b0abcd65ec545701b8793e12bc27dc98042b151a to < 8ac90f6824fc44d2e55a82503ddfc95defb19ae0affected
  • b0abcd65ec545701b8793e12bc27dc98042b151a to < b220bed63330c0e1733dc06ea8e75d5b9962b6b6affected
  • 538c26d9bf70c90edc460d18c81008a4e555925aaffected
  • 5.10.237 to < 5.10.241affected
  • 5.15.181 to < 5.15.190affected
  • 6.1.128 to < 6.1.147affected
  • 6.6.57 to < 6.6.100affected
  • 6.11.4 to < 6.12affected

Linux Linux

Default version status: affected

  • 6.12affected
  • 0 to < 6.12unaffected
  • 5.10.241 to ≤ 5.10.*unaffected
  • 5.15.190 to ≤ 5.15.*unaffected
  • 6.1.147 to ≤ 6.1.*unaffected
  • 6.6.100 to ≤ 6.6.*unaffected
  • 6.12.40 to ≤ 6.12.*unaffected
  • 6.15.8 to ≤ 6.15.*unaffected
  • 6.16 to ≤ *unaffected

References