CVE-2023-53526

jbd2: check 'jh->b_transaction' before removing it from checkpoint

MEDIUM
5.5
CVSS Score
Published: October 1, 2025 at 11:46 AM UTC
Updated: October 15, 2026 at 10:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: jbd2: check 'jh->b_transaction' before removing it from checkpoint Following process will corrupt ext4 image: Step 1: jbd2_journal_commit_transaction __jbd2_journal_insert_checkpoint(jh, commit_transaction) // Put jh into trans1->t_checkpoint_list journal->j_checkpoint_transactions = commit_transaction // Put trans1 into journal->j_checkpoint_transactions Step 2: do_get_write_access test_clear_buffer_dirty(bh) // clear buffer dirty,set jbd dirty __jbd2_journal_file_buffer(jh, transaction) // jh belongs to trans2 Step 3: drop_cache journal_shrink_one_cp_list jbd2_journal_try_remove_checkpoint if (!trylock_buffer(bh)) // lock bh, true if (buffer_dirty(bh)) // buffer is not dirty __jbd2_journal_remove_checkpoint(jh) // remove jh from trans1->t_checkpoint_list Step 4: jbd2_log_do_checkpoint trans1 = journal->j_checkpoint_transactions // jh is not in trans1->t_checkpoint_list jbd2_cleanup_journal_tail(journal) // trans1 is done Step 5: Power cut, trans2 is not committed, jh is lost in next mounting. Fix it by checking 'jh->b_transaction' before remove it from checkpoint.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.15.129 ≤ v < 5.15.1326.1.50 ≤ v < 6.1.546.4.13 ≤ v < 6.56.5.1 ≤ v < 6.5.419b59aeb2af6b47d5c8e69c5dc1d731c8df35446f881b5b1758dc4a35fba4a643c10717d0cf4275.15.1296.1.506.4.136.56.5 rc36.5 rc46.5 rc56.5 rc66.5 rc7b832174b7f89df3ebab02f5b485d00127a0e1a6ee5c768d809a85e9efd0274b2efe69d4970cc0014
Vendor states this is fixed in 2298f2589903a8bc03061b54b31fd97985ab6529 (fixed)
Vendor states this is fixed in 590a809ff743e7bd890ba5fb36bc38e20a36de53 (fixed)
Vendor states this is fixed in dbafe636db415299e54d9dfefc1003bda9e71c9d (fixed)
Vendor states this is fixed in ef5fea70e5915afd64182d155e72bfb4f275e1fc (fixed)
Vendor states this is fixed in 5.15.132 (unaffected)
Vendor states this is fixed in 6.1.54 (unaffected)
Vendor states this is fixed in 6.5 (unaffected)
Vendor states this is fixed in 6.5.4 (unaffected)
Vendor states this is fixed in 6.6 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card