CVE-2025-38627

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-08-22. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

f2fs: compress: fix UAF of f2fs_inode_info in f2fs_free_dic

The decompress_io_ctx may be released asynchronously after I/O completion. If this file is deleted immediately after read, and the kworker of processing post_read_wq has not been executed yet due to high workloads, It is possible that the inode(f2fs_inode_info) is evicted and freed before it is used f2fs_free_dic.

The UAF case as below: Thread A Thread B

  • f2fs_decompress_end_io
  • f2fs_put_dic
  • queue_work
add free_dic work to post_read_wq
  • do_unlink
  • iput
  • evict
  • call_rcu
This file is deleted after read.

Thread C kworker to process post_read_wq

  • rcu_do_batch
  • f2fs_free_inode
  • kmem_cache_free
inode is freed by rcu
  • process_scheduled_works
  • f2fs_late_free_dic
  • f2fs_free_dic
  • f2fs_release_decomp_mem
read (dic->inode)->i_compress_algorithm

This patch store compress_algorithm and sbi in dic to avoid inode UAF.

In addition, the previous solution is deprecated in [1] may cause system hang. [1] https://lore.kernel.org/all/[email protected]

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

August 22, 2025

Last Modified

August 5, 2026

Advisory Details (5)

Auto-updated Jun 6, 2026
No patch confirmed yet.
generic

f2fs: compress: fix UAF of f2fs_inode_info in f2fs_free_dic - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cc81768212cdc509e5a986274db7bc24d18cde19
generic

f2fs: compress: fix UAF of f2fs_inode_info in f2fs_free_dic - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8fae5b6addd5f6895e03797b56e3c7b9f9cd15c9
generic

f2fs: compress: fix UAF of f2fs_inode_info in f2fs_free_dic - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/74cbeeca4f16823ba58c882e1d8b836c0e39c93d
generic

f2fs: compress: fix UAF of f2fs_inode_info in f2fs_free_dic - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5d604d40cd3232b09cb339941ef958e49283ed0a
generic

f2fs: compress: fix UAF of f2fs_inode_info in f2fs_free_dic - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/39868685c2a94a70762bc6d77dc81d781d05bff5

Vendor Advisories for CVE-2025-38627(1)

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

Patch Availability(11)

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.

Weakness Classification(1)

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

All Vendor Advisories

(10)

Data Freshness Timeline

(refreshed 9× in last 7d / 44× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 109 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2025-38627?
CVE-2025-38627 is a high vulnerability published on August 22, 2025. In the Linux kernel, the following vulnerability has been resolved: f2fs: compress: fix UAF of f2fsinodeinfo in f2fsfreedic The decompressioctx may be released asynchronously after I/O completion. If this file is deleted immediately after read, and the kworker of processing postreadwq has not been…
When was CVE-2025-38627 disclosed?
CVE-2025-38627 was first published in the National Vulnerability Database on August 22, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-38627 actively exploited?
CVE-2025-38627 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.9% of all scored CVEs.
What is the CVSS score of CVE-2025-38627?
CVE-2025-38627 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-38627?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-38627, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-38627

Explore →

Is Your Infrastructure Affected by CVE-2025-38627?

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