jbd2: check 'jh->b_transaction' before removing it from checkpoint
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.15.132, 6.1.54, 6.5, 6.5.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From b832174b7f89df3ebab02f5b485d00127a0e1a6e · fixed in ef5fea70e5915afd64182d155e72bfb4f275e1fc; From e5c768d809a85e9efd0274b2efe69d4970cc0014 · fixed in dbafe636db415299e54d9dfefc1003bda9e71c9d; From 46f881b5b1758dc4a35fba4a643c10717d0cf427 · fixed in 2298f2589903a8bc03061b54b31fd97985ab6529; From 46f881b5b1758dc4a35fba4a643c10717d0cf427 · fixed in 590a809ff743e7bd890ba5fb36bc38e20a36de53; From 5.15.129 · fixed in 5.15.132; From 6.1.50 · fixed in 6.1.54; From 6.4.13 · fixed in 6.5
- Linux Linux
6.5
- KernelLinux
fixed in 5.15.132; From 5.16.0 · fixed in 6.1.54; From 6.2.0 · fixed in 6.5.4