Vulnerability · CVE-2025-37839
In the Linux kernel, the following vulnerability has been resolved: jbd2: remove wrong sb->s_sequence check Journal emptiness is not determined by sb->s_sequence == 0 but rather by
Published May 9, 2025 · corrected/updated May 23, 2026 · Linux Linux · evidence confidence high
In the Linux kernel, the following vulnerability has been resolved: jbd2: remove wrong sb->s_sequence check Journal emptiness is not determined by sb->s_sequence == 0 but rather by sb->s_start == 0 (which is set a few lines above). Furthermore 0 is a valid transaction ID so the check can spuriously trigger. Remove the invalid WARN_ON.
Grounded briefings
Catalog interpretations for three audiences. Each brief cites ingested metadata and the original advisories below. They are not independent research and they do not invent exploit steps.
Executive
CVE-2025-37839 is a none public vulnerability record for Linux Linux. It is not currently listed in the CISA Known Exploited catalog. Check the linked vendor or CERT advisories for patch status. This summary is a catalog interpretation of the ingested metadata and cites the original advisories below.
System administrator
Identify whether Linux Linux is in your estate, then compare installed versions with the affected ranges. Affected packages or ranges on record: Linux Linux 24bcc89c7e7c64982e6192b4952a0a92379fc341 <3b4643ffaf72d7a5a357e9bf68b1775f8cfe7e77 (24bcc89c7e7c64982e6192b4952a0a92379fc341 <3b4643ffaf72d7a5a357e9bf68b1775f8cfe7e77). Check the linked vendor or CERT advisories for patch status. Prefer the vendor or distribution advisory linked in Sources before changing production systems. This is a catalog interpretation, not a runbook.
Security analyst
Signals on file: CVSS 0.0, EPSS 33.0%. It is not currently listed in the CISA Known Exploited catalog. Sources contributing to this record: euvd. Public exploit references, when present, are outbound links only and are not proof of active exploitation. This is a catalog interpretation of stored metadata.
Exploitation and remediation
Exploitation evidence
Not listed as known exploited in CISA KEV. Not in CISA KEV or VulnCheck KEV.
Patch and remediation
No required-action text is stored yet. Use the vendor or CERT links in Sources for patch availability.
Safe detection guidance
Compare installed versions with the affected ranges below and verify the advisory from the original publisher. This site stores metadata and outbound links only; it does not ship exploit code or proof-of-concept payloads.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
May 9, 2025 · EUVD
Detected
In the Linux kernel, the following vulnerability has been resolved: jbd2: remove wrong sb->s_sequence check Journal emptiness is not determined by sb->s_sequence == 0 but rather by sb->s_start == 0 (which is set a few lines above). Furthermore 0 is a valid transaction ID so the check can spuriously trigger. Remove the invalid WARN_ON.
May 23, 2026 · EUVD
Updated
In the Linux kernel, the following vulnerability has been resolved: jbd2: remove wrong sb->s_sequence check Journal emptiness is not determined by sb->s_sequence == 0 but rather by sb->s_start == 0 (which is set a few lines above). Furthermore 0 is a valid transaction ID so the check can spuriously trigger. Remove the invalid WARN_ON.
Affected
- vendor Linux Linux 24bcc89c7e7c64982e6192b4952a0a92379fc341 <3b4643ffaf72d7a5a357e9bf68b1775f8cfe7e7724bcc89c7e7c64982e6192b4952a0a92379fc341 <3b4643ffaf72d7a5a357e9bf68b1775f8cfe7e77
Sources
- EUVDVulnerability recordEUVD-2025-14153
In the Linux kernel, the following vulnerability has been resolved: jbd2: remove wrong sb->s_sequence check Journal emptiness is not determined by sb->s_sequence == 0 but rather by sb->s_start == 0 (which is set a few lines above). Furthermore 0 is a valid transaction ID so the c
euvd.enisa.europa.eu