CVE-2025-38051

HIGHNVD 7.07.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2025-06-18. NVD baseline CVSS 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2025-18602 (ENISA EUVD) · GHSA-2xwf-66vq-6mjm (GitHub Security Advisories)Source: ENISA EUVD

7.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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: 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

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---

CVSS v3
7.0
EG Score
7.0HIGHmedium confidence
EG Risk
32
EG Risk 32/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity70% × 45%
Impact severity (EG Severity): CVSS 7.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
11th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.0): severity, escalated by confirmed exploitation. This CVE's 7.0 is its impact severity (EG Severity), not escalated.

EG Severity
7.0 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-30). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 18, 2025

Last Modified

August 5, 2026

Advisory Details (10)

Auto-updated Aug 2, 2026
Patch available.
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4328-1] linux-6.1 security update

https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4327-1] linux security update

https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html
Web page

smb: client: Fix use-after-free in cifs_fill_dirent - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c8623231e0edfcccb7cc6add0288fa0f0594282f
Web page

smb: client: Fix use-after-free in cifs_fill_dirent - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/aee067e88d61eb72e966f094e4749c6b14e7008f
Web page

smb: client: Fix use-after-free in cifs_fill_dirent - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a7a8fe56e932a36f43e031b398aef92341bf5ea0
Web page

smb: client: Fix use-after-free in cifs_fill_dirent - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a24c2f05ac3c5b0aaa539d9d913826d2643dfd0e
Web page

smb: client: Fix use-after-free in cifs_fill_dirent - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9c9aafbacc183598f064902365e107b5e856531f
Web page

smb: client: Fix use-after-free in cifs_fill_dirent - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9bea368648ac46f8593a780760362e40291d22a9
Web page

smb: client: Fix use-after-free in cifs_fill_dirent - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/73cadde98f67f76c5eba00ac0b72c453383cec8b
Web page

smb: client: Fix use-after-free in cifs_fill_dirent - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1b197931fbc821bc7e9e91bf619400db563e3338

Vendor Advisories for CVE-2025-38051(14)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(31)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-raspi-nolpae (5.15.0.1084.82) @ jammy2026-10-31ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-100.100~22.04.1) @ jammy2026-10-31ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1085.85) @ jammy2026-10-31ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-32.32~24.04.1) @ noble2026-10-31ubuntu
ubuntulinux-tools-gcp-fips-5.15 (5.15.0.1090.80) @ jammy2026-10-31ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1094.92) @ jammy2026-10-31ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1094.79) @ jammy2026-10-31ubuntu
ubuntulinux-tools-kvm-5.15 (5.15.0.1086.82) @ jammy2026-10-31ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1094.103~20.04.1) @ focal2026-10-31ubuntu
ubuntulinux-tools-oracle-edge (6.14.0-1013.13~24.04.1) @ noble2026-10-31ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-10-31ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1047.50~22.04.2) @ jammy2026-10-31ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1041.42~22.04.1) @ jammy2026-10-31ubuntu
ubuntulinux-tools-raspi-6.14 (6.14.0-1014.14) @ plucky2026-10-31ubuntu
ubuntulinux-virtual-6.8 (6.8.0-100.100) @ noble2026-10-31ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1041.42) @ noble2026-10-31ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-100.100.1) @ noble2026-10-31ubuntu
redhatkernel-0:6.12.0-55.60.1.el10_02026-02-16redhat
redhatkernel-rt-0:5.14.0-284.156.1.rt14.441.el9_22026-02-11redhat
redhatkernel-0:5.14.0-284.156.1.el9_22026-02-11redhat
redhatkernel-0:5.14.0-570.86.1.el9_62026-02-09redhat
redhatkernel-0:5.14.0-427.109.1.el9_42026-02-04redhat
redhatkernel-rt-0:5.14.0-70.163.1.rt21.235.el9_02026-01-28redhat
redhatkernel-0:5.14.0-70.163.1.el9_02026-01-28redhat
redhatkernel-0:4.18.0-477.126.1.el8_82026-01-28redhat
redhatkernel-rt-0:4.18.0-553.94.1.rt7.435.el8_102026-01-19redhat
redhatkernel-0:4.18.0-553.94.1.el8_102026-01-19redhat
redhatkernel-0:4.18.0-193.181.1.el8_22026-01-15redhat
redhatkernel-0:4.18.0-305.183.1.el8_42026-01-14redhat
redhatkernel-0:4.18.0-372.175.1.el8_62026-01-14redhat
linuxKernel @ 5.4.294 (fixes >=2.6.28)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (46 versions)
  • every version up to 5.10.244-1: fixed in 5.10.244-1
—
linux-6.16.1.106-3~deb11u1 ... 6.1.148-1~deb11u1 (11 versions)
  • every version up to 6.1.153-1~deb11u1: fixed in 6.1.153-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (41 versions)
  • every version up to 6.1.147-1: fixed in 6.1.147-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.32-1: fixed in 6.12.32-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.32-1: fixed in 6.12.32-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(11)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 43× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 203 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 105 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:32 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  2. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  3. 2026-10-31 11:58 UTCEG score recompute
  4. 2026-10-31 11:58 UTCVendor advisory
  5. 2026-10-31 11:58 UTCGHSA enrichmentGHSA-2xwf-66vq-6mjm · GitHub severity HIGH · GitHub CVSS 7.0
  6. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  7. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  8. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  9. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  10. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  11. 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  12. 2026-10-25 16:31 UTCEG score recompute
  13. 2026-10-25 02:29 UTCEG score recompute
  14. 2026-10-25 02:29 UTCVendor advisory
  15. 2026-10-25 02:29 UTCGHSA enrichmentGHSA-2xwf-66vq-6mjm · GitHub severity HIGH · GitHub CVSS 7.0
  16. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  17. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  18. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  19. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  20. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  21. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  22. 2026-10-18 17:00 UTCEG score recompute
  23. 2026-10-18 17:00 UTCVendor advisory
  24. 2026-10-18 16:59 UTCGHSA enrichmentGHSA-2xwf-66vq-6mjm · GitHub severity HIGH · GitHub CVSS 7.0
  25. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
Show 73 more
  1. 2026-10-18 05:36 UTCEG score recompute
  2. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  3. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  4. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  5. 2026-10-13 16:32 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  6. 2026-10-12 17:08 UTCEG score recompute
  7. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  8. 2026-10-11 20:40 UTCEG score recompute
  9. 2026-10-11 18:51 UTCEG score recompute
  10. 2026-10-11 15:28 UTCEG score recompute
  11. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  12. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  13. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  14. 2026-10-08 17:09 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  15. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  16. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  17. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  18. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  19. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  20. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  21. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  22. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  23. 2026-09-27 03:15 UTCOSV refresh
  24. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  25. 2026-09-26 00:24 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  26. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  27. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  28. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  29. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  30. 2026-09-17 19:29 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  31. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  32. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  33. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  34. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  35. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  36. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  37. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  38. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  39. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  40. 2026-09-07 12:48 UTCOSV refresh
  41. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  42. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  43. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  44. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  45. 2026-09-01 04:38 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  46. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  47. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  48. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  49. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  50. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  51. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  52. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  53. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  54. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  55. 2026-08-20 22:01 UTCOSV refresh
  56. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  57. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  58. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  59. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  60. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  61. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  62. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  63. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  64. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  65. 2026-08-08 16:36 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  66. 2026-08-07 16:26 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  67. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  68. 2026-08-05 13:55 UTCEG score recompute
  69. 2026-08-05 13:55 UTCVendor advisory
  70. 2026-08-05 13:55 UTCGHSA enrichmentGHSA-2xwf-66vq-6mjm · GitHub severity HIGH · GitHub CVSS 7.0
  71. 2026-08-04 15:09 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  72. 2026-08-04 10:37 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  73. 2026-08-03 10:35 UTCEPSS rescoreEPSS 0.2% · 8th percentile

Related CVEs(same vendor + same CWE)· as of October 31, 2026

Frequently asked(5)

What is CVE-2025-38051?
CVE-2025-38051 is a high-severity vulnerability; its CVE record was published on June 18, 2025. 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.…
When was the CVE record for CVE-2025-38051 published?
The CVE record for CVE-2025-38051 was published on June 18, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 5, 2026; the record at its source may have been updated since.
Is CVE-2025-38051 actively exploited?
CVE-2025-38051 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-38051?
CVE-2025-38051 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2025-38051?
A fix for CVE-2025-38051 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-38051 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-38051

Explore →

Is Your Infrastructure Affected by CVE-2025-38051?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs