CVE-2025-38051: smb: client: Fix use-after-free in cifs_fill_dirent
Noroxi assessment
Priority: Monitor (action score 28/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.23% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: Linux Linux 1b197931fbc821bc7e9e91bf619400db563e3338, 2.6.28, 73cadde98f67f76c5eba00ac0b72c453383cec8b.
Low priority for now. Upgrade to Linux Linux 1b197931fbc821bc7e9e91bf619400db563e3338, 2.6.28, 73cadde98f67f76c5eba00ac0b72c453383cec8b 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 cifs_fill_dirent There is a race condition in the readdir concurrency process, which may access the rsp buffer after it has been released, triggering the following KASAN warning. ================================================================== BUG: KASAN: slab-use-after-free in cifs_fill_dirent+0xb03/0xb60 [cifs] Read of size 4 at addr ffff8880099b819c by task a.out/342975 CPU: 2 UID: 0 PID: 342975 Comm: a.out Not tainted 6.15.0-rc6+ #240 PREEMPT(full) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.1-2.fc37 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0x53/0x70 print_report+0xce/0x640 kasan_report+0xb8/0xf0 cifs_fill_dirent+0xb03/0xb60 [cifs] cifs_readdir+0x12cb/0x3190 [cifs] iterate_dir+0x1a1/0x520 __x64_sys_getdents+0x134/0x220 do_syscall_64+0x4b/0x110 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7f996f64b9f9 Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 0d f7 c3 0c 00 f7 d8 64 89 8 RSP: 002b:00007f996f53de78 EFLAGS: 00000207 ORIG_RAX: 000000000000004e RAX: ffffffffffffffda RBX: 00007f996f53ecdc RCX: 00007f996f64b9f9 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000003 RBP: 00007f996f53dea0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000207 R12: ffffffffffffff88 R13: 0000000000000000 R14: 00007ffc8cd9a500 R15: 00007f996f51e000 </TASK> Allocated by task 408: kasan_save_stack+0x20/0x40 kasan_save_track+0x14/0x30 __kasan_slab_alloc+0x6e/0x70 kmem_cache_alloc_noprof+0x117/0x3d0 mempool_alloc_noprof+0xf2/0x2c0 cifs_buf_get+0x36/0x80 [cifs] allocate_buffers+0x1d2/0x330 [cifs] cifs_demultiplex_thread+0x22b/0x2690 [cifs] kthread+0x394/0x720 ret_from_fork+0x34/0x70 ret_from_fork_asm+0x1a/0x30 Freed by task 342979: kasan_save_stack+0x20/0x40 kasan_save_track+0x14/0x30 kasan_save_free_info+0x3b/0x60 __kasan_slab_free+0x37/0x50 kmem_cache_free+0x2b8/0x500 cifs_buf_release+0x3c/0x70 [cifs] cifs_readdir+0x1c97/0x3190 [cifs] iterate_dir+0x1a1/0x520 __x64_sys_getdents64+0x134/0x220 do_syscall_64+0x4b/0x110 entry_SYSCALL_64_after_hwframe+0x76/0x7e The buggy address belongs to the object at ffff8880099b8000 which belongs to the cache cifs_request of size 16588 The buggy address is located 412 bytes inside of freed 16588-byte region [ffff8880099b8000, ffff8880099bc0cc) The buggy address belongs to the physical page: page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x99b8 head: order:3 mapcount:0 entire_mapcount:0 nr_pages_mapped:0 pincount:0 anon flags: 0x80000000000040(head|node=0|zone=1) page_type: f5(slab) raw: 0080000000000040 ffff888001e03400 0000000000000000 dead000000000001 raw: 0000000000000000 0000000000010001 00000000f5000000 0000000000000000 head: 0080000000000040 ffff888001e03400 0000000000000000 dead000000000001 head: 0000000000000000 0000000000010001 00000000f5000000 0000000000000000 head: 0080000000000003 ffffea0000266e01 00000000ffffffff 00000000ffffffff head: ffffffffffffffff 0000000000000000 00000000ffffffff 0000000000000008 page dumped because: kasan: bad access detected Memory state around the buggy address: ffff8880099b8080: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff8880099b8100: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb >ffff8880099b8180: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ^ ffff8880099b8200: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff8880099b8280: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ================================================================== POC is available in the link [1]. The problem triggering process is as follows: Process 1 Process 2 ----------------------------------- ---truncated---
- Published
- Jun 18, 2025
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- CWE-416
Report tools
Action score
28
Low priority for now.
- CVSS
- 28 / 40 · 7.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.0
- CNA · Linux
- 7.8
- 0.8 point gap
CVSS:3.1/AV:L/AC:L/PR:L/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.
Is your version affected? Check itNoroxi 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 |
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
- 0f3da51e7046e2eb28992ba65c22d058f571356c, 2.6.28affected
- a364bc0b37f14ffd66c1f982af42990a9d77fa43 and later · before aee067e88d61eb72e966f094e4749c6b14e7008faffected · git
- a364bc0b37f14ffd66c1f982af42990a9d77fa43 and later · before a24c2f05ac3c5b0aaa539d9d913826d2643dfd0eaffected · git
- a364bc0b37f14ffd66c1f982af42990a9d77fa43 and later · before 1b197931fbc821bc7e9e91bf619400db563e3338affected · git
- a364bc0b37f14ffd66c1f982af42990a9d77fa43 and later · before c8623231e0edfcccb7cc6add0288fa0f0594282faffected · git
- a364bc0b37f14ffd66c1f982af42990a9d77fa43 and later · before 73cadde98f67f76c5eba00ac0b72c453383cec8baffected · git
- a364bc0b37f14ffd66c1f982af42990a9d77fa43 and later · before 9bea368648ac46f8593a780760362e40291d22a9affected · git
- a364bc0b37f14ffd66c1f982af42990a9d77fa43 and later · before 9c9aafbacc183598f064902365e107b5e856531faffected · git
- a364bc0b37f14ffd66c1f982af42990a9d77fa43 and later · before a7a8fe56e932a36f43e031b398aef92341bf5ea0affected · git
- 2.6.27.4 and later · before 2.6.28affected · semver
Affected versions · NVD (9)
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 kernel2.6.27.4 and later · before 5.4.294
- linux linux kernel5.5 and later · before 5.10.238
- linux linux kernel5.11 and later · before 5.15.185
- linux linux kernel5.16 and later · before 6.1.141
- linux linux kernel6.2 and later · before 6.6.93
- linux linux kernel6.7 and later · before 6.12.31
- linux linux kernel6.13 and later · before 6.14.9
- linux linux kernel6.15
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | bpftool | before 4.18.0-553.94.1.el8_10 | 4.18.0-553.94.1.el8_10 |
| AlmaLinux:8 | kernel | before 4.18.0-553.94.1.el8_10 | 4.18.0-553.94.1.el8_10 |
| AlmaLinux:8 | kernel-abi-stablelists | before 4.18.0-553.94.1.el8_10 | 4.18.0-553.94.1.el8_10 |
| AlmaLinux:8 | kernel-core | before 4.18.0-553.94.1.el8_10 | 4.18.0-553.94.1.el8_10 |
| AlmaLinux:8 | kernel-cross-headers | before 4.18.0-553.94.1.el8_10 | 4.18.0-553.94.1.el8_10 |
| AlmaLinux:8 | kernel-debug | before 4.18.0-553.94.1.el8_10 | 4.18.0-553.94.1.el8_10 |
| AlmaLinux:8 | kernel-debug-core | before 4.18.0-553.94.1.el8_10 | 4.18.0-553.94.1.el8_10 |
| AlmaLinux:8 | kernel-debug-devel | before 4.18.0-553.94.1.el8_10 | 4.18.0-553.94.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules | before 4.18.0-553.94.1.el8_10 | 4.18.0-553.94.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules-extra | before 4.18.0-553.94.1.el8_10 | 4.18.0-553.94.1.el8_10 |
| AlmaLinux:8 | kernel-devel | before 4.18.0-553.94.1.el8_10 | 4.18.0-553.94.1.el8_10 |
| AlmaLinux:8 | kernel-doc | before 4.18.0-553.94.1.el8_10 | 4.18.0-553.94.1.el8_10 |
| AlmaLinux:8 | kernel-headers | before 4.18.0-553.94.1.el8_10 | 4.18.0-553.94.1.el8_10 |
| AlmaLinux:8 | kernel-modules | before 4.18.0-553.94.1.el8_10 | 4.18.0-553.94.1.el8_10 |
| AlmaLinux:8 | kernel-modules-extra | before 4.18.0-553.94.1.el8_10 | 4.18.0-553.94.1.el8_10 |
| AlmaLinux:8 | kernel-rt | before 4.18.0-553.94.1.rt7.435.el8_10 | 4.18.0-553.94.1.rt7.435.el8_10 |
| AlmaLinux:8 | kernel-rt-core | before 4.18.0-553.94.1.rt7.435.el8_10 | 4.18.0-553.94.1.rt7.435.el8_10 |
| AlmaLinux:8 | kernel-rt-debug | before 4.18.0-553.94.1.rt7.435.el8_10 | 4.18.0-553.94.1.rt7.435.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-core | before 4.18.0-553.94.1.rt7.435.el8_10 | 4.18.0-553.94.1.rt7.435.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-devel | before 4.18.0-553.94.1.rt7.435.el8_10 | 4.18.0-553.94.1.rt7.435.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules | before 4.18.0-553.94.1.rt7.435.el8_10 | 4.18.0-553.94.1.rt7.435.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules-extra | before 4.18.0-553.94.1.rt7.435.el8_10 | 4.18.0-553.94.1.rt7.435.el8_10 |
| AlmaLinux:8 | kernel-rt-devel | before 4.18.0-553.94.1.rt7.435.el8_10 | 4.18.0-553.94.1.rt7.435.el8_10 |
| AlmaLinux:8 | kernel-rt-modules | before 4.18.0-553.94.1.rt7.435.el8_10 | 4.18.0-553.94.1.rt7.435.el8_10 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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
Published before and after this one in the same product
- ← EarlierCVE-2025-38048Jun 18, 2025 · virtio_ring: Fix data race by tagging event_triggered as racy for KCSAN18Monitor
- ← EarlierCVE-2025-38050Jun 18, 2025 · mm/hugetlb: fix kernel NULL pointer dereference when replacing free hugetlb folios22Monitor
- Later →CVE-2025-38053Jun 18, 2025 · idpf: fix null-ptr-deref in idpf_features_check22Monitor
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 | 1b197931fbc821bc7e9e91bf619400db563e3338 | Vendor (CNA) |
| Linux Linux | 2.6.28 | Vendor (CNA) |
| Linux Linux | 73cadde98f67f76c5eba00ac0b72c453383cec8b | Vendor (CNA) |
| Linux Linux | 9bea368648ac46f8593a780760362e40291d22a9 | Vendor (CNA) |
| Linux Linux | 9c9aafbacc183598f064902365e107b5e856531f | Vendor (CNA) |
| Linux Linux | a24c2f05ac3c5b0aaa539d9d913826d2643dfd0e | Vendor (CNA) |
| Linux Linux | a7a8fe56e932a36f43e031b398aef92341bf5ea0 | Vendor (CNA) |
| Linux Linux | aee067e88d61eb72e966f094e4749c6b14e7008f | Vendor (CNA) |
| Linux Linux | c8623231e0edfcccb7cc6add0288fa0f0594282f | Vendor (CNA) |
| almalinux:bpftool | 4.18.0-553.94.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel | 4.18.0-553.94.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-abi-stablelists | 4.18.0-553.94.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-core | 4.18.0-553.94.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-cross-headers | 4.18.0-553.94.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug | 4.18.0-553.94.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-core | 4.18.0-553.94.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-devel | 4.18.0-553.94.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules | 4.18.0-553.94.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules-extra | 4.18.0-553.94.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-devel | 4.18.0-553.94.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-doc | 4.18.0-553.94.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| debian:linux | 6.1.147-1 · Debian:12 | Package registry (OSV) |
| red hat:bpftool | 0:4.18.0-305.183.1.el8_4 · Red Hat:rhel_aus:8.4::baseos | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:4.18.0-305.183.1.el8_4 · Red Hat:rhel_aus:8.4::baseos | Package registry (OSV) |
| red hat:kernel | 0:4.18.0-305.183.1.el8_4 · Red Hat:rhel_aus:8.4::baseos | Package registry (OSV) |
| red hat:kernel-abi-stablelists | 0:4.18.0-305.183.1.el8_4 · Red Hat:rhel_aus:8.4::baseos | Package registry (OSV) |
| red hat:kernel-core | 0:4.18.0-305.183.1.el8_4 · Red Hat:rhel_aus:8.4::baseos | Package registry (OSV) |
| red hat:kernel-debug | 0:4.18.0-305.183.1.el8_4 · Red Hat:rhel_aus:8.4::baseos | Package registry (OSV) |
| red hat:kernel-debug-core | 0:4.18.0-305.183.1.el8_4 · Red Hat:rhel_aus:8.4::baseos | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:4.18.0-305.183.1.el8_4 · Red Hat:rhel_aus:8.4::baseos | Package registry (OSV) |
+6
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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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.
- Special conditions such as timing or configuration are required.
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
- High
- 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:H/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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (9 more)Show less
- git.kernel.org/stable/c/73cadde98f67f76c5eba00ac0b72c453383cec8b
- git.kernel.org/stable/c/9bea368648ac46f8593a780760362e40291d22a9
- git.kernel.org/stable/c/9c9aafbacc183598f064902365e107b5e856531f
- git.kernel.org/stable/c/a24c2f05ac3c5b0aaa539d9d913826d2643dfd0e
- git.kernel.org/stable/c/a7a8fe56e932a36f43e031b398aef92341bf5ea0
- git.kernel.org/stable/c/aee067e88d61eb72e966f094e4749c6b14e7008f
- git.kernel.org/stable/c/c8623231e0edfcccb7cc6add0288fa0f0594282f
- 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.