Menu

Star on GitHub · 3.2k

CVE-2023-53526

7.8 · HIGH

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_jour…

Published Oct 1, 2025EPSS 0.15%

Overview

CVE-2023-53526 is a high-severity vulnerability. It was published on October 1, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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_j

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2023-53526?

CVE-2023-53526 is a high-severity vulnerability. It was published on October 1, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2023-53526?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2023-53526?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2023-53526?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2023-53526 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2023

View all