CVE-2025-38580: ext4: fix inode use after free in ext4_end_io_rsv_work()
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.
Security readout for executives and security teams
Plain-English summary
A Linux ext4 filesystem flaw can leave background work referencing an inode after it has been freed. This kernel use-after-free could affect system stability and security. The assigned CVSS 7.8 score rates potential confidentiality, integrity, and availability impacts as high, but the supplied sources do not document successful exploitation.
Executive priority
Treat this as a high-priority kernel maintenance issue, especially on shared Linux systems using ext4. It is not currently supported as an emergency internet-wide exploitation event. Accelerate vendor-confirmed updates while avoiding unsupported version assumptions from the ambiguous upstream range data.
Technical view
An unnecessary deferred completion worker can be queued when no extent conversion is required. After ext4_finish_bio() runs, the inode may be freed before ext4_end_io_rsv_work() accesses it. The fixes align completion checks, avoid workers for empty or certain failed operations, and avoid journal abort attempts during emergency state.
Likely exposure
Exposure applies to systems running affected Linux kernel releases where ext4 is used. The CVSS vector indicates a local, low-privileged attack surface rather than direct remote exposure. The supplied affected-version data is ambiguous, so distribution-specific kernel builds must be checked against vendor guidance and the referenced fixes.
Exploitation context
This CVE is not listed as KEV, and the supplied sources provide no evidence of active exploitation or a public exploit. CVSS indicates local access, low complexity, low privileges, and no user interaction. Those metrics describe assessed conditions, not proof that exploitation is practical.
Researcher notes
The vulnerable lifecycle involves deferred I/O completion, i_rsv_conversion_list, ext4_finish_bio(), and later worker access to a freed inode. Review should focus on whether downstream kernels contain equivalent fixes. The source bundle does not identify a CWE, triggering workload, observed attack chain, or distribution-specific fixed package versions.
Mitigation direction
Apply a vendor-supported kernel update containing the applicable stable fix, then reboot into the updated kernel.
Use distribution guidance to identify the correct fixed kernel for each release and support channel.
Prioritize multi-user or untrusted-workload systems that use ext4 filesystems.
Validation and detection
Inventory running kernel versions and identify systems using ext4 filesystems.
Compare vendor kernel changelogs with the three referenced stable fixes.
Confirm the updated kernel is active after reboot, not merely installed.
Review kernel logs for ext4 errors, crashes, or use-after-free reports.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-38580 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
4Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.