CVE-2025-22113

Advisory lineage Upstream: 0 Downstream: 32
Analyzed
Published: 16 Apr 2025, 14:12
Last modified:11 May 2026, 21:13

Vulnerability Summary

Overall Risk (default)
low
22/100
CVSS Score
5.5 MEDIUM
v3.1 (nvd)
EPSS Score
0.02% LOW
0% probability 0.00%
KEV
Not listed
Ransomware
No reports
Public exploits
None found
Dark Web
Not detected

Timeline

16 Apr 2025, 14:12
Published
Vulnerability first disclosed
11 May 2026, 21:13
Last Modified
Vulnerability information updated

Description

In the Linux kernel, the following vulnerability has been resolved: ext4: avoid journaling sb update on error if journal is destroying Presently we always BUG_ON if trying to start a transaction on a journal marked with JBD2_UNMOUNT, since this should never happen. However, while ltp running stress tests, it was observed that in case of some error handling paths, it is possible for update_super_work to start a transaction after the journal is destroyed eg: (umount) ext4_kill_sb kill_block_super generic_shutdown_super sync_filesystem /* commits all txns */ evict_inodes /* might start a new txn */ ext4_put_super flush_work(&sbi->s_sb_upd_work) /* flush the workqueue */ jbd2_journal_destroy journal_kill_thread journal->j_flags |= JBD2_UNMOUNT; jbd2_journal_commit_transaction jbd2_journal_get_descriptor_buffer jbd2_journal_bmap ext4_journal_bmap ext4_map_blocks ... ext4_inode_error ext4_handle_error schedule_work(&sbi->s_sb_upd_work) /* work queue kicks in */ update_super_work jbd2_journal_start start_this_handle BUG_ON(journal->j_flags & JBD2_UNMOUNT) Hence, introduce a new mount flag to indicate journal is destroying and only do a journaled (and deferred) update of sb if this flag is not set. Otherwise, just fallback to an un-journaled commit. Further, in the journal destroy path, we have the following sequence: 1. Set mount flag indicating journal is destroying 2. force a commit and wait for it 3. flush pending sb updates This sequence is important as it ensures that, after this point, there is no sb update that might be journaled so it is safe to update the sb outside the journal. (To avoid race discussed in 2d01ddc86606) Also, we don't need a similar check in ext4_grp_locked_error since it is only called from mballoc and AFAICT it would be always valid to schedule work here.

CVSS Metrics

  • v3.1•MEDIUM•Score: 5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

EPSS Trends

Current EPSS score: 0.02%• Percentile: 6%

Affected Systems

  • linux•linux

    ≥ 2d01ddc86606564fb08c56e3bc93a0693895f710, < eddca44ddf810e27f0c96913aa3cc92ebd679ddb | ≥ 2d01ddc86606564fb08c56e3bc93a0693895f710, < db05767b5bc307143d99fe2afd8c43af58d2ebef | ≥ 2d01ddc86606564fb08c56e3bc93a0693895f710, < ce2f26e73783b4a7c46a86e3af5b5c8de0971790 | 5.11

  • linux•linux_kernel

    ≥ 5.11.1, < 6.12.46 | ≥ 6.13, < 6.14.2 | 5.11 | 5.11:rc4 | 5.11:rc5 | 5.11:rc6 | 5.11:rc7

References (3)