Answer in brief
CVE-2025-38580 records a High severity (CVSS 7.8) vulnerability in ext4: fix inode use after free in ext4_end_io_rsv_work(). 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 | >=ce51afb8cc5e1867ea0dfdf5e92ddbe31a1fad5d <ac999862b98a0f49e858e509f776be51406f1e77 || >=ce51afb8cc5e1867ea0dfdf5e92ddbe31a1fad5d <469c44e66e2110054949609dde095788320139d0 || >=ce51afb8cc5e1867ea0dfdf5e92ddbe31a1fad5d <c678bdc998754589cea2e6afab9401d7d8312ac4 | ac999862b98a0f49e858e509f776be51406f1e77, 469c44e66e2110054949609dde095788320139d0, c678bdc998754589cea2e6afab9401d7d8312ac4 |
| Linux/Linuxgeneric | 6.15 | Not reported |
Published upstream
Aug 19, 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: ext4: fix inode use after free in ext4_end_io_rsv_work() In ext4_io_end_defer_completion(), check if io_end->list_vec is empty to avoid adding an io_end that requires no conversion to the i_rsv_conversion_list, which in turn prevents starting an unnecessary worker. An ext4_emergency_state() check is also added to avoid attempting to abort the journal in an emergency state. Additionally, ext4_put_io_end_defer() is refactored to call ext4_io_end_defer_completion() directly instead of being open-coded. This also prevents starting an unnecessary worker when EXT4_IO_END_FAILED is set but data_err=abort is not enabled. This ensures that the check in ext4_put_io_end_defer() is consistent with the check in ext4_end_bio(). Otherwise, we might add an io_end to the i_rsv_conversion_list and then call ext4_finish_bio(), after which the inode could be freed before ext4_end_io_rsv_work() is called, triggering a use-after-free issue.
Quoted source text, attributed separately from HOL analysis.