CVE-2025-22113: ext4: avoid journaling sb update on error if journal is destroying
ext4: avoid journaling sb update on error if journal is destroying
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
Introduce a new mount flag indicating the JBD2 journal is destroying, and set journal->j_flags |= JBD2_UNMOUNT during the journal destroy path so update_super_work/start_this_handle does not begin new transactions after this point.
Linux kernel ext4 / JBD2 journal journal->j_flags |= JBD2_UNMOUNT (mount flag indicating journal is destroying) = enable - Compensating control
Ensure the journaled sb update workqueue is drained during shutdown/destroy by flushing pending sb updates: flush_work(&sbi->s_sb_upd_work) before forcing a commit and waiting, so no new sb update work can start a transaction after the journal is marked JBD2_UNMOUNT.
Event History
Frequently Asked Questions
What is the severity of CVE-2025-22113?
CVE-2025-22113 is classified as a medium-severity vulnerability in the Linux kernel.
How do I fix CVE-2025-22113?
To fix CVE-2025-22113, users should upgrade their Linux kernel to the latest version that includes the patch for this vulnerability.
What is the impact of CVE-2025-22113?
The impact of CVE-2025-22113 may potentially lead to kernel crashes in systems using the ext4 filesystem under specific error conditions.
Is CVE-2025-22113 exploitable remotely?
CVE-2025-22113 is not considered remotely exploitable as it requires local access to the system with the affected kernel.
Which versions of the Linux kernel are affected by CVE-2025-22113?
CVE-2025-22113 affects various versions of the Linux kernel prior to the release of the patched version.