[CVE-2026-72225][LOW] jbd2: fix integer underflow in jbd2_journal_initialize_fast_commit()

[AL-KERNEL <alkernel@kernelcve.org>]

CVE: CVE-2026-72225
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: jbd2: fix integer underflow in jbd2_journal_initialize_fast_commit()
Commit: e144ad0250f77e23e28949587b8b57e40dc3b512
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e144ad0250f77e23e28949587b8b57e40dc3b512
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72225
Analysis date: Sat, 15 Aug 2026 03:15:02 -0400
ActionableScore: 1
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: YES

Summary:
No one-sentence report phrase was found.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-72225 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72225

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: LOW
Manual review required: YES

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-72225	LOW	CHECK WITH IMPACT FROM ORIG NN MODERATE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H';CWE-191;CWE-190;CWE-682;*CWE-20;Other CVSS 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '5.5';DESCR 'An unsigned integer underflow in jbd2_journal_initialize_fast_commit can occur when the configured number of fast commit blocks is larger than journal j_last. The wrapped subtraction can bypass the journal size check and corrupt internal journal accounting fields such as j_last, j_fc_first, and j_free, leading to a journal abort. For the CVSS the PR:L is used only for the paranoid score because some deployments may allow a less privileged user to provide a crafted filesystem image to an automount or storage management service. The typical base case is PR:H because mounting ext4 filesystems normally requires administrative privileges. The issue is not network reachable. Impact is denial of service through mount failure or journal abort, with no clear UAF, OOB write, arbitrary write, or privilege escalation primitive visible from the patch context.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 1)	YES	OOB DISK SIMPLEFIX  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	YES	NO	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=1

1. ActionableScore
* Conservative score: 1
* Paranoid score: 2 if a deployment allows a less privileged user to supply crafted ext4 images to an automount or storage service. Not selected as the main actionable score because this is not shown by the patch.
* Final recommended bucket: **Ordinary Moderate / Low-like**::

2. Signal breakdown
* Important filesystem/storage path: +1. jbd2/ext4 journal initialization is a storage integrity path.
* Availability impact realistic: +1. The underflow can corrupt journal accounting fields and lead to journal abort or mount failure.
* Requires admin/root/CAP_SYS_ADMIN in typical deployments: -2. Reliable triggering normally requires mounting a crafted or corrupted ext4 filesystem.
* No generic memory corruption signal. The described corruption is journal accounting state, not UAF, OOB write, arbitrary write, type confusion, or page-cache corruption.
* No privilege escalation signal. No concrete LPE primitive is visible from the patch context.

3. Reachability analysis
The realistic trigger is local and privileged: an administrator or process with mount authority mounts an ext4 filesystem whose fast commit configuration makes num_fc_blks exceed journal->j_last. A paranoid PR:L scenario exists only if a local user can feed crafted filesystem images into a privileged automount, container storage, or disk-management service. The path is not network reachable. The affected code is in an important and common filesystem stack, but the malformed mount requirement limits practical exposure.

4. Severity interpretation
This behaves like an ordinary Moderate or Low-like storage DoS, not an Important-class kernel vulnerability. Theoretical impact is journal state corruption and abort, but realistic evidence points to denial of service or mount failure only. There is no demonstrated memory lifetime bug, attacker-controlled overwrite, shared-page corruption, or privilege escalation path.

5. One-sentence report phrase
An unsigned integer underflow in jbd2 fast commit initialization can bypass journal size validation for malformed ext4 journal geometry, corrupt internal journal accounting, and cause journal abort or mount failure, but exploitation normally requires privileged mount access.

6. Manual review recommendation
NO MANUAL CHECK NEEDED. NO MANUAL CHECK REQUIRED COULD BE AUTOCLOSED.
Reason: no network reachability, no concrete memory corruption primitive, no LPE path, and typical triggering requires administrative filesystem mount privileges.

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: jbd2: fix integer underflow in jbd2_journal_initialize_fast_commit()
Commit: e144ad0250f77e23e28949587b8b57e40dc3b512
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e144ad0250f77e23e28949587b8b57e40dc3b512

Commit description:

jbd2_journal_initialize_fast_commit() validates journal capacity by
checking (journal->j_last - num_fc_blks < JBD2_MIN_JOURNAL_BLOCKS).
Both j_last and num_fc_blks are unsigned, so when num_fc_blks exceeds
j_last the subtraction wraps to a large value, bypassing the bounds
check.

The resulting underflow corrupts j_last, j_fc_first, and j_free,
leading to journal abort.

Fix by checking num_fc_blks against j_last before the subtraction,
returning -EFSCORRUPTED.

Fixes: 6866d7b ("ext4 / jbd2: add fast commit initialization")
Reported-by: Yuhao Jiang <danisjiang@gmail.com>
Cc: stable@vger.kernel.org
Signed-off-by: Junrui Luo <moonafterrain@outlook.com>
Fixes: e029c5f ("ext4: make num of fast commit blocks configurable")
Reviewed-by: Baokun Li <libaokun@linux.alibaba.com>
Fixes: e029c5f ("ext4: make num of fast commit blocks configurable")
Reviewed-by: Zhang Yi <yi.zhang@huawei.com>
Reviewed-by: Jan Kara <jack@suse.cz>
Link: https://patch.msgid.link/SYBPR01MB7881663C927DE9D7BBF4D1DFAF062@SYBPR01MB7881.ausprd01.prod.outlook.com
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Changed files:
  fs/jbd2/journal.c

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e144ad0250f77e23e28949587b8b57e40dc3b512

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-72225 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72225

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L
  The Best / paranoid CVSS vector: AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 5.5

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: unknown
  Paranoid ActionableScore: 1

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: LOW
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): LOW

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).