Answer in brief
CVE-2025-38627 records a High severity (CVSS 7.8) vulnerability in f2fs: compress: fix UAF of f2fs_inode_info in f2fs_free_dic. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=bff139b49d9f70c1ac5384aac94554846aa834de <74cbeeca4f16823ba58c882e1d8b836c0e39c93d || >=bff139b49d9f70c1ac5384aac94554846aa834de <5d604d40cd3232b09cb339941ef958e49283ed0a || >=bff139b49d9f70c1ac5384aac94554846aa834de <cc81768212cdc509e5a986274db7bc24d18cde19 || >=bff139b49d9f70c1ac5384aac94554846aa834de <8fae5b6addd5f6895e03797b56e3c7b9f9cd15c9 || >=bff139b49d9f70c1ac5384aac94554846aa834de <39868685c2a94a70762bc6d77dc81d781d05bff5 | 74cbeeca4f16823ba58c882e1d8b836c0e39c93d, 5d604d40cd3232b09cb339941ef958e49283ed0a, cc81768212cdc509e5a986274db7bc24d18cde19, 8fae5b6addd5f6895e03797b56e3c7b9f9cd15c9, 39868685c2a94a70762bc6d77dc81d781d05bff5 |
| Linux/Linuxgeneric | 6.0 | Not reported |
Published upstream
Aug 22, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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]
Quoted source text, attributed separately from HOL analysis.