CVE-2025-38488: smb: client: fix use-after-free in crypt_message when using async crypto
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.71% (FIRST EPSS); higher than 53.3% of all records.
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 15a0a5de49507062bc3be4014a403d8cea5533de, 2a76bc2b24ed889a689fb1c9015307bf16aafb5b, 5.10.241; cbl2 kernel 5.15.186.1-1 on CBL Mariner 2.0 5.15.200.1-1.
- Severity is disputed: the assigning authority (CNA) scores it 9.8, NVD 7.8.
Low priority for now. Upgrade to Linux Linux 15a0a5de49507062bc3be4014a403d8cea5533de, 2a76bc2b24ed889a689fb1c9015307bf16aafb5b, 5.10.241; cbl2 kernel 5.15.186.1-1 on CBL Mariner 2.0 5.15.200.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- BDU:2025-10805
- SUSE-SU-2025:03601-1
- SUSE-SU-2025:3725-1
- SUSE-SU-2026:0939-1
- SUSE-SU-2026:0940-1
- SUSE-SU-2026:0941-1
- SUSE-SU-2026:0951-1
- SUSE-SU-2026:0953-1
- SUSE-SU-2026:0954-1
- SUSE-SU-2026:0958-1
- SUSE-SU-2026:0983-1
- SUSE-SU-2026:0992-1
- SUSE-SU-2026:1000-1
- SUSE-SU-2026:1002-1
- SUSE-SU-2026:1039-1
- SUSE-SU-2026:1044-1
- SUSE-SU-2026:1046-1
- SUSE-SU-2026:1049-1
- SUSE-SU-2026:1073-1
- SUSE-SU-2026:1083-1
- Published
- Jul 28, 2025
- Updated
- Aug 5, 2026
- EPSS
- 0.7% · 53th percentile
- CWE
- CWE-416
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
CNA vs NVD score
- NVD
- 7.8
- CNA · Linux
- 9.8
- 2.0 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux11.0
- linux linux kernel5.15.181 and later · before 5.15.190
- linux linux kernel6.1.128 and later · before 6.1.147
- linux linux kernel6.6.57 and later · before 6.6.100
- linux linux kernel5.10.237 and later · before 5.10.241
- linux linux kernel6.13 and later · before 6.15.8
- linux linux kernel6.11.4 and later · before 6.12.40
- linux linux kernel6.16
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 538c26d9bf70c90edc460d18c81008a4e555925a, 6.12affected
- 8f14a476abba13144df5434871a7225fd29af633 and later · before 5d047b12f86cc3b9fde1171c02d9bccf4dba0632affected · git
- ef51c0d544b1518b35364480317ab6d3468f205d and later · before 6550b2bef095d0dd2d2c8390d2ea4c3837028833affected · git
- bce966530fd5542bbb422cb45ecb775f7a1a6bc3 and later · before 9a1d3e8d40f151c2d5a5f40c410e6e433f62f438affected · git
- 0809fb86ad13b29e1d6d491364fc7ea4fb545995 and later · before 15a0a5de49507062bc3be4014a403d8cea5533deaffected · git
- b0abcd65ec545701b8793e12bc27dc98042b151a and later · before 2a76bc2b24ed889a689fb1c9015307bf16aafb5baffected · git
- b0abcd65ec545701b8793e12bc27dc98042b151a and later · before 8ac90f6824fc44d2e55a82503ddfc95defb19ae0affected · git
- b0abcd65ec545701b8793e12bc27dc98042b151a and later · before b220bed63330c0e1733dc06ea8e75d5b9962b6b6affected · git
- 5.10.237 and later · before 5.10.241affected · semver
- 5.15.181 and later · before 5.15.190affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.147-1 | 6.1.147-1 |
| Debian:13 | linux | before 6.12.41-1 | 6.12.41-1 |
| Debian:14 | linux | before 6.16.3-1 | 6.16.3-1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kgraft-patch-SLE12-SP5_Update_65 | before 15-2.1 | 15-2.1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kgraft-patch-SLE12-SP5_Update_67 | before 14-2.1 | 14-2.1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kgraft-patch-SLE12-SP5_Update_68 | before 12-2.1 | 12-2.1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kgraft-patch-SLE12-SP5_Update_70 | before 11-2.1 | 11-2.1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kgraft-patch-SLE12-SP5_Update_72 | before 7-2.1 | 7-2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_36 | before 16-150400.2.2 | 16-150400.2.2 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_37 | before 16-150400.2.2 | 16-150400.2.2 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_44 | before 9-150400.2.1 | 9-150400.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP5 | kernel-livepatch-SLE15-SP5_Update_24 | before 16-150500.2.2 | 16-150500.2.2 |
| SUSE:Linux Enterprise Live Patching 15 SP5 | kernel-livepatch-SLE15-SP5_Update_25 | before 15-150500.2.2 | 15-150500.2.2 |
| SUSE:Linux Enterprise Live Patching 15 SP5 | kernel-livepatch-SLE15-SP5_Update_27 | before 14-150500.2.1 | 14-150500.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP5 | kernel-livepatch-SLE15-SP5_Update_29 | before 11-150500.2.1 | 11-150500.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_10 | before 14-150600.2.2 | 14-150600.2.2 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_12 | before 13-150600.2.1 | 13-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_13 | before 11-150600.2.1 | 11-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_14 | before 7-150600.2.1 | 7-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_15 | before 7-150600.2.1 | 7-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7_Update_0 | before 12-150700.3.33.1 | 12-150700.3.33.1 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7_Update_1 | before 12-150700.2.1 | 12-150700.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7_Update_2 | before 11-150700.2.1 | 11-150700.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7_Update_4 | before 7-150700.2.1 | 7-150700.2.1 |
+33
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
- CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV83Now
Published before and after this one in the same product
- ← EarlierCVE-2025-38486Jul 28, 2025 · soundwire: Revert "soundwire: qcom: Add set_channel_map api support"22Monitor
- ← EarlierCVE-2025-38487Jul 28, 2025 · soc: aspeed: lpc-snoop: Don't disable channels that aren't enabled22Monitor
- Later →CVE-2025-38489Jul 28, 2025 · s390/bpf: Fix bpf_arch_text_poke() with new_addr == NULL again22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 15a0a5de49507062bc3be4014a403d8cea5533de | Vendor (CNA) |
| Linux Linux | 2a76bc2b24ed889a689fb1c9015307bf16aafb5b | Vendor (CNA) |
| Linux Linux | 5.10.241 | Vendor (CNA) |
| Linux Linux | 5.15.190 | Vendor (CNA) |
| Linux Linux | 5d047b12f86cc3b9fde1171c02d9bccf4dba0632 | Vendor (CNA) |
| Linux Linux | 6.1.147 | Vendor (CNA) |
| Linux Linux | 6.12 | Vendor (CNA) |
| Linux Linux | 6.6.100 | Vendor (CNA) |
| Linux Linux | 6550b2bef095d0dd2d2c8390d2ea4c3837028833 | Vendor (CNA) |
| Linux Linux | 8ac90f6824fc44d2e55a82503ddfc95defb19ae0 | Vendor (CNA) |
| Linux Linux | 9a1d3e8d40f151c2d5a5f40c410e6e433f62f438 | Vendor (CNA) |
| Linux Linux | b220bed63330c0e1733dc06ea8e75d5b9962b6b6 | Vendor (CNA) |
| cbl2 kernel 5.15.186.1-1 on CBL Mariner 2.0 | 5.15.200.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.147-1 · Debian:12 | Package registry (OSV) |
| suse:kernel-64kb | 6.4.0-150700.53.19.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7 | Package registry (OSV) |
| suse:kernel-default | 6.4.0-150700.53.19.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7 | Package registry (OSV) |
| suse:kernel-default-base | 6.4.0-150700.53.19.1.150700.17.13.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7 | Package registry (OSV) |
| suse:kernel-docs | 6.4.0-150700.53.19.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP7 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP7_Update_5 | 1-150700.15.3.1 · SUSE:Linux Enterprise Live Patching 15 SP7 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP7-RT_Update_5 | 1-150700.1.3.1 · SUSE:Linux Enterprise Live Patching 15 SP7 | Package registry (OSV) |
| suse:kernel-obs-build | 6.4.0-150700.53.19.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP7 | Package registry (OSV) |
| suse:kernel-rt | 6.4.0-150700.7.19.1 · SUSE:Real Time Module 15 SP7 | Package registry (OSV) |
| suse:kernel-source | 6.4.0-150700.53.19.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7 | Package registry (OSV) |
| suse:kernel-source-rt | 6.4.0-150700.7.19.1 · SUSE:Real Time Module 15 SP7 | Package registry (OSV) |
| suse:kernel-syms | 6.4.0-150700.53.19.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP7 | Package registry (OSV) |
| suse:kernel-zfcpdump | 6.4.0-150700.53.19.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/2a76bc2b24ed889a689fb1c9015307bf16aafb5b
- git.kernel.org/stable/c/5d047b12f86cc3b9fde1171c02d9bccf4dba0632
- git.kernel.org/stable/c/6550b2bef095d0dd2d2c8390d2ea4c3837028833
- git.kernel.org/stable/c/8ac90f6824fc44d2e55a82503ddfc95defb19ae0
- git.kernel.org/stable/c/9a1d3e8d40f151c2d5a5f40c410e6e433f62f438
- git.kernel.org/stable/c/b220bed63330c0e1733dc06ea8e75d5b9962b6b6
- lists.debian.org/debian-lts-announce/2025/10/msg00007.html
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.