BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2023-53526High confidence

jbd2: check 'jh->b_transaction' before removing it from checkpoint

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 131 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 5 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.15% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 131 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

13 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 9 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.5.6-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.55-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.5.6-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.5.6-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcp-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-hwe-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-intelAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatency-hwe-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2023-53526 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: jbd2: check 'jh->b_transaction' before removing it from checkpoint
122 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel as a component of Red Hat Enterprise Linux 6
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6
  • kernel-bootwrapper as a component of Red Hat Enterprise Linux 6
  • kernel-debug as a component of Red Hat Enterprise Linux 6
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 6
  • kernel-devel as a component of Red Hat Enterprise Linux 6
  • kernel-doc as a component of Red Hat Enterprise Linux 6
  • kernel-firmware as a component of Red Hat Enterprise Linux 6
  • kernel-headers as a component of Red Hat Enterprise Linux 6
  • kernel-kdump as a component of Red Hat Enterprise Linux 6
  • kernel-kdump-devel as a component of Red Hat Enterprise Linux 6
  • kernel.src as a component of Red Hat Enterprise Linux 6
Summary
A flaw was found in the Linux kernel's jbd2 journaling subsystem. A race condition during checkpoint handling could lead to a buffer being incorrectly removed from a transaction's checkpoint list. If a system experiences a crash or power loss before the new transaction is fully committed, this vulnerability can result in corruption of the ext4 filesystem, potentially causing loss of data or metadata.
Remediation
To mitigate this issue, prevent module jbd2 from being loaded. Please see https://access.redhat.com/solutions/41278 for how to blacklist a kernel module to prevent it from loading automatically.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-32736

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 131 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-0349Dell Avamar und NetWorker: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Dell Avamar und Dell NetWorker ausnutzen, um Angriffe zu starten, die die Integrität, Vertraulichkeit und Verfügbarkeit von Systemen beeinträchtigen.

Official advisory ↗
BSI · German · WID-SEC-2025-2187Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht nähere beschriebene Effekte zu verursachen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20251008Security Bulletin 08 Oct 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 08 Oct 2025, published on 8 October 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1032Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2023-53507 Référence CVE CVE-2023-53508 https://www.cve.org/CVERecord?id=CVE-2023-53508 Référence CVE CVE-2023-53510 https://www.cve.org/CVERecord?id=CVE-2023-53510 Référence CVE CVE-2023-53515 https://www.cve.org/CVERecord?id=CVE-2023-53515 Référence CVE CVE-2023-53516 https://www.cve.org/CVERecord?id=CVE-2023-53516 Référence CVE CVE-2023-53518 https://www.cve.org/CVERecord?id=CVE-2023-53518 Référence CVE CVE-2023-53519 https://www.cve.org/CVERecord?id=CVE-2023-53519 Référence CVE CVE-2023-53520 https://www.cve.org/CVERecord?id=CVE-2023-53520 Référence CVE CVE-2023-53523 https://www.cve.org/CVERecord?id=CVE-2023-53523 Référence CVE CVE-2023-53526 https://www.cve.org/CVERecord?id=CVE-2023-53526 Référence CVE CVE-2023-53527 https://www.cve.org/CVERecord?id=CVE-2023-53527 Référence CVE CVE-2023-53528 https://www.cve.org/CVERecord?id=CVE-2023-53528 Référence CVE CVE-2023-53530 https://www.cve.org/CVERecord?id=CVE-2023-53530 Référence CVE CVE-2023-53531 https://www.cve.org/CVERecord?id=CVE-2023-53531 Référence CVE CVE-2023-53533 https://www.cve.org/CVERecord?id=CVE-2023-53533 Référence CVE CVE-2023-53534 https://www.cve.org/CVERecord?id=CVE-2023-53534 Référence CVE CVE-2023-53538 https://www.cve.org/CVERecord?id=CVE-2023-53538 Référence CVE CVE-2023-53539 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1009Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2023-53507 Référence CVE CVE-2023-53508 https://www.cve.org/CVERecord?id=CVE-2023-53508 Référence CVE CVE-2023-53510 https://www.cve.org/CVERecord?id=CVE-2023-53510 Référence CVE CVE-2023-53515 https://www.cve.org/CVERecord?id=CVE-2023-53515 Référence CVE CVE-2023-53516 https://www.cve.org/CVERecord?id=CVE-2023-53516 Référence CVE CVE-2023-53518 https://www.cve.org/CVERecord?id=CVE-2023-53518 Référence CVE CVE-2023-53519 https://www.cve.org/CVERecord?id=CVE-2023-53519 Référence CVE CVE-2023-53520 https://www.cve.org/CVERecord?id=CVE-2023-53520 Référence CVE CVE-2023-53523 https://www.cve.org/CVERecord?id=CVE-2023-53523 Référence CVE CVE-2023-53526 https://www.cve.org/CVERecord?id=CVE-2023-53526 Référence CVE CVE-2023-53527 https://www.cve.org/CVERecord?id=CVE-2023-53527 Référence CVE CVE-2023-53528 https://www.cve.org/CVERecord?id=CVE-2023-53528 Référence CVE CVE-2023-53530 https://www.cve.org/CVERecord?id=CVE-2023-53530 Référence CVE CVE-2023-53531 https://www.cve.org/CVERecord?id=CVE-2023-53531 Référence CVE CVE-2023-53538 https://www.cve.org/CVERecord?id=CVE-2023-53538 Référence CVE CVE-2023-53539 https://www.cve.org/CVERecord?id=CVE-2023-53539 Référence CVE CVE-2023-53540 https://www.cve.org/CVERecord?id=CVE-2023-53540 Référence CVE CVE-2023-53541 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0921Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2023-53515 Référence CVE CVE-2023-53516 https://www.cve.org/CVERecord?id=CVE-2023-53516 Référence CVE CVE-2023-53518 https://www.cve.org/CVERecord?id=CVE-2023-53518 Référence CVE CVE-2023-53519 https://www.cve.org/CVERecord?id=CVE-2023-53519 Référence CVE CVE-2023-53520 https://www.cve.org/CVERecord?id=CVE-2023-53520 Référence CVE CVE-2023-53521 https://www.cve.org/CVERecord?id=CVE-2023-53521 Référence CVE CVE-2023-53523 https://www.cve.org/CVERecord?id=CVE-2023-53523 Référence CVE CVE-2023-53524 https://www.cve.org/CVERecord?id=CVE-2023-53524 Référence CVE CVE-2023-53525 https://www.cve.org/CVERecord?id=CVE-2023-53525 Référence CVE CVE-2023-53526 https://www.cve.org/CVERecord?id=CVE-2023-53526 Référence CVE CVE-2023-53527 https://www.cve.org/CVERecord?id=CVE-2023-53527 Référence CVE CVE-2023-53528 https://www.cve.org/CVERecord?id=CVE-2023-53528 Référence CVE CVE-2023-53530 https://www.cve.org/CVERecord?id=CVE-2023-53530 Référence CVE CVE-2023-53531 https://www.cve.org/CVERecord?id=CVE-2023-53531 Référence CVE CVE-2023-5633 https://www.cve.org/CVERecord?id=CVE-2023-5633 Référence CVE CVE-2024-26583 https://www.cve.org/CVERecord?id=CVE-2024-26583 Référence CVE CVE-2024-26584 https://www.cve.org/CVERecord?id=CVE-2024-26584 Référence CVE CVE-2024-26661 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0895Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2023-53515 Référence CVE CVE-2023-53516 https://www.cve.org/CVERecord?id=CVE-2023-53516 Référence CVE CVE-2023-53518 https://www.cve.org/CVERecord?id=CVE-2023-53518 Référence CVE CVE-2023-53519 https://www.cve.org/CVERecord?id=CVE-2023-53519 Référence CVE CVE-2023-53520 https://www.cve.org/CVERecord?id=CVE-2023-53520 Référence CVE CVE-2023-53521 https://www.cve.org/CVERecord?id=CVE-2023-53521 Référence CVE CVE-2023-53523 https://www.cve.org/CVERecord?id=CVE-2023-53523 Référence CVE CVE-2023-53524 https://www.cve.org/CVERecord?id=CVE-2023-53524 Référence CVE CVE-2023-53525 https://www.cve.org/CVERecord?id=CVE-2023-53525 Référence CVE CVE-2023-53526 https://www.cve.org/CVERecord?id=CVE-2023-53526 Référence CVE CVE-2023-53527 https://www.cve.org/CVERecord?id=CVE-2023-53527 Référence CVE CVE-2023-53528 https://www.cve.org/CVERecord?id=CVE-2023-53528 Référence CVE CVE-2023-53530 https://www.cve.org/CVERecord?id=CVE-2023-53530 Référence CVE CVE-2023-53531 https://www.cve.org/CVERecord?id=CVE-2023-53531 Référence CVE CVE-2023-53532 https://www.cve.org/CVERecord?id=CVE-2023-53532 Référence CVE CVE-2023-5633 https://www.cve.org/CVERecord?id=CVE-2023-5633 Référence CVE CVE-2024-26583 https://www.cve.org/CVERecord?id=CVE-2024-26583 Référence CVE CVE-2024-26584 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-025437LinuxのLinux Kernelにおける不特定の脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。jbd2においては、チェックポイントからトランザクションを削除する前に『jh-b_transaction』を確認する必要があります。次の手順によってext4イメージが破損する可能性があります。手順1では、jbd2_journal_commit_transaction関数内で__jbd2_journal_insert_checkpoint(jh, commit_transaction)によってjhがtrans1-t_checkpoint_listに追加され、journal-j_checkpoint_transactionsがcommit_transactionに設定され、trans1がjournal-j_checkpoint_transactionsに格納されます。手順2では、do_get_write_accessでtest_clear_buffer_dirty(bh)によりバッファのdirtyフラグがクリアされjbdがdirtyにセットされ、__jbd2_journal_file_buffer(jh, transaction)によりjhがtrans2に属します。手順3では、drop_cacheでjournal_shrink_one_cp_listが呼ばれ、jbd2_journal_try_remove_checkpoint関数内でtrylock_buffer(bh)が成功し、buffer_dirty(bh)はfalseであるため、__jbd2_journal_remove_checkpoint(jh)によりjhがtrans1-t_checkpoint_listから削除されます。手順4では、jbd2_log_do_checkpointでtrans1 = journal-j_checkpoint_transactionsとなり、jhはtrans1-t_checkpoint_listに存在しなくなり、jbd2_cleanup_journal_tail(journal)でtrans1が完了します。手順5で電源断が発生し、trans2はコミットされません。そのため次回マウント時にjhが失われる問題が発生します。対策として、チェックポイントから削除する前に『jh-b_transaction』を必ず確認するように修正されました。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 6.5, 5.15.132 ≤ 5.15.*, 6.1.54 ≤ 6.1.*, 6.5.4 ≤ 6.5.*, 6.6 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
To mitigate this issue, prevent module jbd2 from being loaded. Please see https://access.redhat.com/solutions/41278 for how to blacklist a kernel module to prevent it from loading automatically.
04

Evidence and provenance

Published 1 Oct 2025 · Last source change 5 Aug 2026, 09:14 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-32736
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceUnavailable
NVD statusNVD modified after enrichment

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2025-32736↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2023-53526 · cve.blacktree.nl