CVE-2025-38580

published 19 Aug 2025 · updated 5 Aug 2026

ext4: fix inode use after free in ext4_end_io_rsv_work()

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 469c44e66e2110054949609dde095788320139d0, Kernel ac999862b98a0f49e858e509f776be51406f1e77 and Kernel c678bdc998754589cea2e6afab9401d7d8312ac4.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=6.15, >=ce51afb8cc5e1867ea0dfdf5e92ddbe31a1fad5d <469c44e66e2110054949609dde095788320139d0, >=ce51afb8cc5e1867ea0dfdf5e92ddbe31a1fad5d <ac999862b98a0f49e858e509f776be51406f1e77, >=ce51afb8cc5e1867ea0dfdf5e92ddbe31a1fad5d <c678bdc998754589cea2e6afab9401d7d8312ac4469c44e66e2110054949609dde095788320139d0, ac999862b98a0f49e858e509f776be51406f1e77, c678bdc998754589cea2e6afab9401d7d8312ac4

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2025-38580 severity on Zeptric[![CVE-2025-38580](https://zeptric.io/badge/cve/CVE-2025-38580.svg)](https://zeptric.io/cve/CVE-2025-38580)