CVE-2025-22113
- Source
- https://nvd.nist.gov/vuln/detail/CVE-2025-22113
- Import Source
- https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2025-22113.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/CVE-2025-22113
- Downstream
- Related
- Published
- 2025-04-16T14:12:59Z
- Modified
- 2025-10-10T09:03:28.703854Z
- Summary
- ext4: avoid journaling sb update on error if journal is destroying
- Details
-
In the Linux kernel, the following vulnerability has been resolved:
ext4: avoid journaling sb update on error if journal is destroying
Presently we always BUGON if trying to start a transaction on a journal marked with JBD2UNMOUNT, 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 updatesuperwork to start a transaction after the journal is destroyed eg:
(umount) ext4killsb killblocksuper genericshutdownsuper syncfilesystem /* commits all txns */ evictinodes /* might start a new txn / ext4_put_super flush_work(&sbi->s_sb_upd_work) / flush the workqueue */ jbd2journaldestroy journalkillthread journal->jflags |= JBD2UNMOUNT; jbd2journalcommittransaction jbd2journalgetdescriptorbuffer jbd2journalbmap ext4journalbmap ext4mapblocks ... ext4inodeerror ext4handleerror schedulework(&sbi->ssbupd_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:
- Set mount flag indicating journal is destroying
- force a commit and wait for it
- 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 ext4grplocked_error since it is only called from mballoc and AFAICT it would be always valid to schedule work here.
- References
Affected packages
Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected ranges
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced2d01ddc86606564fb08c56e3bc93a0693895f710Fixededdca44ddf810e27f0c96913aa3cc92ebd679ddb
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced2d01ddc86606564fb08c56e3bc93a0693895f710Fixeddb05767b5bc307143d99fe2afd8c43af58d2ebef
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced2d01ddc86606564fb08c56e3bc93a0693895f710Fixedce2f26e73783b4a7c46a86e3af5b5c8de0971790