VulnerabilityPublished 22 Dec 2025Updated 30 Jul 2026

CVE-2025-68337: Linux kernel · jbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted

Source GCVE Database

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-75fx-9v9v-4p3x

What to do

AI-suggested

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.

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.

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.

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.

References

Community reviews

Loading reviews…