CVE-2025-38577

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Score 5.5 from GitHub Security Advisory published 2025-08-19. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2025-26099 (ENISA EUVD) · GHSA-6fm3-hv4h-3737 (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

f2fs: fix to avoid panic in f2fs_evict_inode

As syzbot [1] reported as below:

R10: 0000000000000100 R11: 0000000000000206 R12: 00007ffe17473450 R13: 00007f28b1c10854 R14: 000000000000dae5 R15: 00007ffe17474520 ---[ end trace 0000000000000000 ]--- ================================================================== BUG: KASAN: use-after-free in __list_del_entry_valid+0xa6/0x130 lib/list_debug.c:62 Read of size 8 at addr ffff88812d962278 by task syz-executor/564

CPU: 1 PID: 564 Comm: syz-executor Tainted: G W 6.1.129-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025 Call Trace: __dump_stack+0x21/0x24 lib/dump_stack.c:88 dump_stack_lvl+0xee/0x158 lib/dump_stack.c:106 print_address_description+0x71/0x210 mm/kasan/report.c:316 print_report+0x4a/0x60 mm/kasan/report.c:427 kasan_report+0x122/0x150 mm/kasan/report.c:531 __asan_report_load8_noabort+0x14/0x20 mm/kasan/report_generic.c:351 __list_del_entry_valid+0xa6/0x130 lib/list_debug.c:62 __list_del_entry include/linux/list.h:134 [inline] list_del_init include/linux/list.h:206 [inline] f2fs_inode_synced+0xf7/0x2e0 fs/f2fs/super.c:1531 f2fs_update_inode+0x74/0x1c40 fs/f2fs/inode.c:585 f2fs_update_inode_page+0x137/0x170 fs/f2fs/inode.c:703 f2fs_write_inode+0x4ec/0x770 fs/f2fs/inode.c:731 write_inode fs/fs-writeback.c:1460 [inline] __writeback_single_inode+0x4a0/0xab0 fs/fs-writeback.c:1677 writeback_single_inode+0x221/0x8b0 fs/fs-writeback.c:1733 sync_inode_metadata+0xb6/0x110 fs/fs-writeback.c:2789 f2fs_sync_inode_meta+0x16d/0x2a0 fs/f2fs/checkpoint.c:1159 block_operations fs/f2fs/checkpoint.c:1269 [inline] f2fs_write_checkpoint+0xca3/0x2100 fs/f2fs/checkpoint.c:1658 kill_f2fs_super+0x231/0x390 fs/f2fs/super.c:4668 deactivate_locked_super+0x98/0x100 fs/super.c:332 deactivate_super+0xaf/0xe0 fs/super.c:363 cleanup_mnt+0x45f/0x4e0 fs/namespace.c:1186 __cleanup_mnt+0x19/0x20 fs/namespace.c:1193 task_work_run+0x1c6/0x230 kernel/task_work.c:203 exit_task_work include/linux/task_work.h:39 [inline] do_exit+0x9fb/0x2410 kernel/exit.c:871 do_group_exit+0x210/0x2d0 kernel/exit.c:1021 __do_sys_exit_group kernel/exit.c:1032 [inline] __se_sys_exit_group kernel/exit.c:1030 [inline] __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1030 x64_sys_call+0x7b4/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:232 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x68/0xd2 RIP: 0033:0x7f28b1b8e169 Code: Unable to access opcode bytes at 0x7f28b1b8e13f. RSP: 002b:00007ffe174710a8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7 RAX: ffffffffffffffda RBX: 00007f28b1c10879 RCX: 00007f28b1b8e169 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000001 RBP: 0000000000000002 R08: 00007ffe1746ee47 R09: 00007ffe17472360 R10: 0000000000000009 R11: 0000000000000246 R12: 00007ffe17472360 R13: 00007f28b1c10854 R14: 000000000000dae5 R15: 00007ffe17474520

Allocated by task 569: kasan_save_stack mm/kasan/common.c:45 [inline] kasan_set_track+0x4b/0x70 mm/kasan/common.c:52 kasan_save_alloc_info+0x25/0x30 mm/kasan/generic.c:505 __kasan_slab_alloc+0x72/0x80 mm/kasan/common.c:328 kasan_slab_alloc include/linux/kasan.h:201 [inline] slab_post_alloc_hook+0x4f/0x2c0 mm/slab.h:737 slab_alloc_node mm/slub.c:3398 [inline] slab_alloc mm/slub.c:3406 [inline] __kmem_cache_alloc_lru mm/slub.c:3413 [inline] kmem_cache_alloc_lru+0x104/0x220 mm/slub.c:3429 alloc_inode_sb include/linux/fs.h:3245 [inline] f2fs_alloc_inode+0x2d/0x340 fs/f2fs/super.c:1419 alloc_inode fs/inode.c:261 [inline] iget_locked+0x186/0x880 fs/inode.c:1373 f2fs_iget+0x55/0x4c60 fs/f2fs/inode.c:483 f2fs_lookup+0x366/0xab0 fs/f2fs/namei.c:487 __lookup_slow+0x2a3/0x3d0 fs/namei.c:1690 lookup_slow+0x57/0x70 fs/namei.c:1707 walk_component+0x2e6/0x410 fs/namei ---truncated---

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 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 BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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
8th
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 (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-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-24). 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 (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

August 19, 2025

Last Modified

August 5, 2026

Advisory Details (10)

Auto-updated Aug 2, 2026
Patch available.
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

f2fs: fix to avoid panic in f2fs_evict_inode - kernel/git/stable/linux.git - Linux kernel stable tree

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

f2fs: fix to avoid panic in f2fs_evict_inode - kernel/git/stable/linux.git - Linux kernel stable tree

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

f2fs: fix to avoid panic in f2fs_evict_inode - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/97df495d754116c8c28ac6a4112f831727bde887
Web page

f2fs: fix to avoid panic in f2fs_evict_inode - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9535e440fe5bc6c5ac7cfb407e53bf788b8bf8d4
Web page

f2fs: fix to avoid panic in f2fs_evict_inode - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/880ef748e78a1eb7df2d8e11a9ef21e98bcaabe5
Web page

f2fs: fix to avoid panic in f2fs_evict_inode - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5cd99d5aa3d39086bdb53eb5c52df16e98b101a0
Web page

f2fs: fix to avoid panic in f2fs_evict_inode - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4732ca17c17f5062426cfa982f43593e6b81963b
Web page

f2fs: fix to avoid panic in f2fs_evict_inode - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/42f9ea16aea8b49febaa87950a006a1792209f38
Web page

f2fs: fix to avoid panic in f2fs_evict_inode - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/15df59809c54fbd687cdf27efbd2103a937459be

Vendor Advisories for CVE-2025-38577(1)

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-realtime-5.15 (5.15.0.1096.100) @ jammy2026-10-23ubuntu
ubuntulinux-tools-oem-6.14 (6.14.0-1016.16) @ noble2026-10-23ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.14.0-1016.16~24.04.1) @ noble2026-10-23ubuntu
ubuntulinux-tools-raspi-6.14 (6.14.0-1018.18) @ plucky2026-10-23ubuntu
ubuntulinux-tools-gkeop-5.15 (5.15.0.1080.79) @ jammy2026-10-23ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1101.86) @ jammy2026-10-23ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1101.99) @ jammy2026-10-23ubuntu
ubuntulinux-tools-kvm-5.15 (5.15.0.1089.85) @ jammy2026-10-23ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1091.89) @ jammy2026-10-23ubuntu
ubuntulinux-tools-azure-6.14 (6.14.0-1017.17) @ plucky2026-10-23ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1047.50~22.04.2) @ jammy2026-10-23ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1041.42) @ noble2026-10-23ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-100.100+fips1) @ noble2026-10-23ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1047.50+fips1) @ noble2026-10-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1046.49.1) @ noble2026-10-23ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-100.100.1) @ noble2026-10-23ubuntu
ubuntulinux-tools-gke-64k-6.8 (6.8.0-1043.48) @ noble2026-10-23ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1023.24) @ noble2026-10-23ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1046.52) @ noble2026-10-23ubuntu
ubuntulinux-tools-oracle-edge (6.14.0-1017.17~24.04.1) @ noble2026-10-23ubuntu
ubuntulinux-tools-gcp-fips-5.15 (5.15.0.1097.87) @ jammy2026-10-23ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1102.111~20.04.1) @ focal2026-10-23ubuntu
ubuntulinux-virtual-6.8 (6.8.0-100.100) @ noble2026-10-23ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1041.42~22.04.1) @ jammy2026-10-23ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1061 (5.15.0-1061.65) @ jammy2026-10-23ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-36.36) @ plucky2026-10-23ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1046.52+fips1) @ noble2026-10-23ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1043.44) @ noble2026-10-23ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-10-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-100.100~22.04.1) @ jammy2026-10-23ubuntu
linuxKernel @ 5.4.297 (fixes >=4.8.0)—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 (42 versions)
  • every version up to 6.1.148-1: fixed in 6.1.148-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1, 6.12.41-1, 6.12.43-1~bpo12+1
  • every version up to 6.12.43-1: fixed in 6.12.43-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.16~rc7-1~exp1 (62 versions)
  • every version up to 6.16.3-1: fixed in 6.16.3-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(24)

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-38577?
CVE-2025-38577 is a medium-severity vulnerability; its CVE record was published on August 19, 2025. In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid panic in f2fs_evict_inode As syzbot [1] reported as below: R10: 0000000000000100 R11: 0000000000000206 R12: 00007ffe17473450 R13: 00007f28b1c10854 R14: 000000000000dae5 R15: 00007ffe17474520 </TASK> ---[ end…
When was the CVE record for CVE-2025-38577 published?
The CVE record for CVE-2025-38577 was published on August 19, 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-38577 actively exploited?
CVE-2025-38577 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-38577?
CVE-2025-38577 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-38577?
A fix for CVE-2025-38577 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-38577 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-38577

Explore →

Is Your Infrastructure Affected by CVE-2025-38577?

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

Book a Demo →Browse All CVEs