CVE-2023-53526
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-10-01

Last updated on: 2026-04-06

Assigner: kernel.org

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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-10-01
Last Modified
2026-04-06
Generated
2026-05-07
AI Q&A
2025-10-01
EPSS Evaluated
2026-05-05
NVD
CVE-2023-53526
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel From 5.15.160 (inc) to 5.16 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability in the Linux kernel's jbd2 journaling system involves improper handling of journal transactions during checkpoint removal. Specifically, the system fails to check the 'jh->b_transaction' before removing it from the checkpoint list, which can lead to corruption of the ext4 filesystem image. The issue occurs through a sequence of steps where a journal transaction is committed and inserted into a checkpoint list, then another transaction modifies the buffer, and during cache dropping, the system incorrectly removes a journal head from the checkpoint list without verifying its transaction association. This can cause the journal head to be lost after a power cut, leading to filesystem corruption. The fix involves adding a check for 'jh->b_transaction' before removing it from the checkpoint.


How can this vulnerability impact me? :

This vulnerability can lead to corruption of the ext4 filesystem image on affected Linux systems. If a power cut occurs at a critical moment during journal transaction processing, uncommitted transactions may be lost, causing data loss or filesystem corruption. This can result in system instability, data integrity issues, and potential downtime while recovering or repairing the filesystem.


What immediate steps should I take to mitigate this vulnerability?

Apply the patch or update to the fixed Linux kernel version that includes the check for 'jh->b_transaction' before removing it from the checkpoint in jbd2. This prevents corruption of the ext4 image and data loss after power cuts.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart