CVE-2025-38627f2fs: compress: fix UAF of f2fs_inode_info in f2fs_free_dic
- 7.8HighCVSS base score
- 0.19%Exploitation in 30 daysEPSS · top 92% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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]
Timeline
ID reserved
By Linux
- 4 months later
· 4 months later
Published
- 12 months later
· 12 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.19% · top 92% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected bff139b49d9f70c1ac5384aac94554846aa834de – < 74cbeeca4f16823ba58c882e1d8b836c0e39c93d
- affected bff139b49d9f70c1ac5384aac94554846aa834de – < 5d604d40cd3232b09cb339941ef958e49283ed0a
- affected bff139b49d9f70c1ac5384aac94554846aa834de – < cc81768212cdc509e5a986274db7bc24d18cde19
- affected bff139b49d9f70c1ac5384aac94554846aa834de – < 8fae5b6addd5f6895e03797b56e3c7b9f9cd15c9
- affected bff139b49d9f70c1ac5384aac94554846aa834de – < 39868685c2a94a70762bc6d77dc81d781d05bff5
- affected 6.0
- unaffected < 6.0
- unaffected 6.1.175 – ≤ 6.1.*
- unaffected 6.6.118 – ≤ 6.6.*
- unaffected 6.12.78 – ≤ 6.12.*
- unaffected 6.16.1 – ≤ 6.16.*
- unaffected 6.17 – ≤ *
References
References5
- https://git.kernel.org/stable/c/74cbeeca4f16823ba58c882e1d8b836c0e39c93d (opens in a new tab)
- https://git.kernel.org/stable/c/5d604d40cd3232b09cb339941ef958e49283ed0a (opens in a new tab)
- https://git.kernel.org/stable/c/cc81768212cdc509e5a986274db7bc24d18cde19 (opens in a new tab)
- https://git.kernel.org/stable/c/8fae5b6addd5f6895e03797b56e3c7b9f9cd15c9 (opens in a new tab)
- https://git.kernel.org/stable/c/39868685c2a94a70762bc6d77dc81d781d05bff5 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-25574 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-38627)Record last updated .