Medium

CVE-2025-22113 — ext4: avoid journaling sb update on error if journal is destroying

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.

Published Apr 16, 2025 · Updated Oct 21, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: Linux

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.2% (30-day exploitation probability)+2
Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.25%

ahead of 16% of scored CVEs · Oct 28, 2026

Affects

Linux

Linux and 1 more

CVSS base

5.5

Medium · 1 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

Documented patch — git.kernel.org (NIST National Vulnerability Database)
Documented patch — git.kernel.org (NIST National Vulnerability Database)
Documented patch — git.kernel.org (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Linux Linux, Linux Linux Kernel).
Apply the fixed version or the patch documented under Remediation.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Linux	Linux	≥ 2d01ddc86606564fb08c56e3bc93a0693895f710 and < b6d27f4869c9c4dedce0ba1c719d6c748a4ecc68≥ 2d01ddc86606564fb08c56e3bc93a0693895f710 and < eddca44ddf810e27f0c96913aa3cc92ebd679ddb≥ 2d01ddc86606564fb08c56e3bc93a0693895f710 and < db05767b5bc307143d99fe2afd8c43af58d2ebef≥ 2d01ddc86606564fb08c56e3bc93a0693895f710 and < ce2f26e73783b4a7c46a86e3af5b5c8de0971790version 5.11	Vulnerable	CVE Program (cve.org) e CISA ADP
Linux	Linux Kernel	≥ 5.11.1 and < 6.12.46≥ 6.13 and < 6.14.2version 5.11version 5.11-rc4version 5.11-rc5version 5.11-rc6version 5.11-rc7	Vulnerable	NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Local

Attack complexity

Low

Privileges required

Low

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
5.5	CVSS 3.1	Medium	1.8	3.6	nvd@nist.gov via NIST National Vulnerability Database

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov)

EPSS over time FIRST

Oct 21, 2026 → Oct 28, 2026 · 8 reading(s) · max 0.25%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.

endpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

2026
Affected products added · linux/linux
Oct 21, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 21, 2026
Fix documented
Oct 21, 2026 · NIST National Vulnerability Database
CVSS changed · 5.5
Oct 21, 2026 · NIST National Vulnerability Database
Source status changed · → Modified
Oct 21, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 21, 2026 · NIST National Vulnerability Database
2025
CVE published
Apr 16, 2025 · Linux

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 21, 2026 – Oct 21, 2026

References

4 on the record

git.kernel.org/stable/c/ce2f26e73783b4a7c46a86e3af5b5c8de0971790
Patch, NIST National Vulnerability Database
git.kernel.org/stable/c/db05767b5bc307143d99fe2afd8c43af58d2ebef
Patch, NIST National Vulnerability Database
git.kernel.org/stable/c/eddca44ddf810e27f0c96913aa3cc92ebd679ddb
Patch, NIST National Vulnerability Database
git.kernel.org/stable/c/b6d27f4869c9c4dedce0ba1c719d6c748a4ecc68
NIST National Vulnerability Database

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 1d
Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 1d
Unknown CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 1d
Unknown CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 1d
Unknown CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 1d
Unknown CVE-2026-99210 accel/rocket: clear rdev on device init failure 1d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No CISA SSVC assessment.
No CWE classification.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-22113 is "ext4: avoid journaling sb update on error if journal is destroying", rated Medium. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.5 describes technical severity. EPSS 0.25% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.