In the Linux kernel, the following vulnerability has been resolved: jbd2: avoid bug_on in jbd2_journal_get_create_access() when file system… (CVE-2025-68337)
A vulnerability in the Linux kernel's jbd2 journaling subsystem could cause a kernel crash (BUG_ON) when the file system is corrupted. This occurs due to improper handling of file system inconsistencies, leading to a kernel BUG triggered by jbd2_journal_get_create_access(). The issue arises in scenarios where file system data is inconsistent, such as when a block bitmap is not set correctly, causing block allocation conflicts. The fix replaces the immediate kernel crash with a journaling abort to handle such abnormal conditions more gracefully.
AI Analysis
Technical Summary
The vulnerability in the Linux kernel's jbd2 component involves a kernel BUG triggered by the function jbd2_journal_get_create_access() when the file system is corrupted. Specifically, under certain file system inconsistencies (e.g., block bitmap not set for a referenced block), the kernel triggers a BUG_ON condition leading to a crash. This occurs in errors=continue mode with storage failures, where the journaling code's assertion (J_ASSERT) fails under abnormal conditions. The patch changes the behavior to abort the journaling transaction instead of crashing the kernel, improving stability when encountering corrupted file system states.
Potential Impact
This vulnerability can cause a denial of service by crashing the Linux kernel when the file system is corrupted and certain conditions are met. There is no impact on confidentiality or integrity reported. The crash occurs due to a kernel BUG_ON triggered by file system inconsistencies during journaling operations, potentially leading to system unavailability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, avoid operating in conditions that may cause file system corruption or use error handling modes that trigger this issue. Monitor vendor channels for updates and apply official kernel patches once released.
In the Linux kernel, the following vulnerability has been resolved: jbd2: avoid bug_on in jbd2_journal_get_create_access() when file system… (CVE-2025-68337)
Description
A vulnerability in the Linux kernel's jbd2 journaling subsystem could cause a kernel crash (BUG_ON) when the file system is corrupted. This occurs due to improper handling of file system inconsistencies, leading to a kernel BUG triggered by jbd2_journal_get_create_access(). The issue arises in scenarios where file system data is inconsistent, such as when a block bitmap is not set correctly, causing block allocation conflicts. The fix replaces the immediate kernel crash with a journaling abort to handle such abnormal conditions more gracefully.
CVSS v3.1
Score 7.5high
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel's jbd2 component involves a kernel BUG triggered by the function jbd2_journal_get_create_access() when the file system is corrupted. Specifically, under certain file system inconsistencies (e.g., block bitmap not set for a referenced block), the kernel triggers a BUG_ON condition leading to a crash. This occurs in errors=continue mode with storage failures, where the journaling code's assertion (J_ASSERT) fails under abnormal conditions. The patch changes the behavior to abort the journaling transaction instead of crashing the kernel, improving stability when encountering corrupted file system states.
Potential Impact
This vulnerability can cause a denial of service by crashing the Linux kernel when the file system is corrupted and certain conditions are met. There is no impact on confidentiality or integrity reported. The crash occurs due to a kernel BUG_ON triggered by file system inconsistencies during journaling operations, potentially leading to system unavailability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, avoid operating in conditions that may cause file system corruption or use error handling modes that trigger this issue. Monitor vendor channels for updates and apply official kernel patches once released.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-75fx-9v9v-4p3x
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2025-68337"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6a6b72d29c2644c7f8477cd9
Added to database: 07/30/2026, 15:50:42 UTC
Last enriched: 07/30/2026, 18:52:36 UTC
Last updated: 09/10/2026, 19:26:54 UTC
Views: 11
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.