CVE-2023-53526
Last modified
CVE-2023-53526 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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.. EPSS estimates a 0.14% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 5.15.129, < 5.15.132 |
| Linux | Linux Kernel | >= 6.1.50, < 6.1.54 |
| Linux | Linux Kernel | >= 6.4.13, < 6.5 |
| Linux | Linux Kernel | >= 6.5.1, < 6.5.4 |
| Linux | Linux Kernel | 6.5 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2023-53526?
How severe is CVE-2023-53526?
How do I fix CVE-2023-53526?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2023
- CVE-2023-53520In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2023-53521In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2023-53522In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-53523In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53524In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-53525In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53527In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53528In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53529In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-5353Improper Access Control in GitHub repository salesagility/su…6.5
- CVE-2023-53530In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53531In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2023-53526?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
