jbd2: check 'jh->b_transaction' before removing it from checkpoint
Summary
| CVE | CVE-2023-53526 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2025-10-01 12:15:57 UTC |
| Updated | 2026-04-06 13:27:15 UTC |
| 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. |
Risk And Classification
Primary CVSS: v3.1 5.5 MEDIUM from [email protected]
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Problem Types: NVD-CWE-noinfo
CVSS v3.1 Breakdown
Attack Vector
LocalAttack Complexity
LowPrivileges Required
LowUser Interaction
NoneScope
UnchangedConfidentiality
NoneIntegrity
NoneAvailability
HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Operating System | Linux | Linux Kernel | All | All | All | All |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected b832174b7f89df3ebab02f5b485d00127a0e1a6e ef5fea70e5915afd64182d155e72bfb4f275e1fc git | Not specified |
| CNA | Linux | Linux | affected e5c768d809a85e9efd0274b2efe69d4970cc0014 dbafe636db415299e54d9dfefc1003bda9e71c9d git | Not specified |
| CNA | Linux | Linux | affected 46f881b5b1758dc4a35fba4a643c10717d0cf427 2298f2589903a8bc03061b54b31fd97985ab6529 git | Not specified |
| CNA | Linux | Linux | affected 46f881b5b1758dc4a35fba4a643c10717d0cf427 590a809ff743e7bd890ba5fb36bc38e20a36de53 git | Not specified |
| CNA | Linux | Linux | affected 019b59aeb2af6b47d5c8e69c5dc1d731c8df0354 git | Not specified |
| CNA | Linux | Linux | affected 6.5 | Not specified |
| CNA | Linux | Linux | unaffected 6.5 semver | Not specified |
| CNA | Linux | Linux | unaffected 5.15.132 5.15.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.54 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.5.4 6.5.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/2298f2589903a8bc03061b54b31fd97985ab6529 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/590a809ff743e7bd890ba5fb36bc38e20a36de53 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/ef5fea70e5915afd64182d155e72bfb4f275e1fc | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/dbafe636db415299e54d9dfefc1003bda9e71c9d | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.