ZDF
Sign inSign up

Vulnerabilities

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 · catalog updated May 23, 2026 · Linux Linux

Check if you run it

No confirmed exploitation is on record for CVE-2025-37839. EPSS is 0.33%. Act only if a listed version of Linux Linux is installed.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
None0.0
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.33%
Remediation
Version ranges on file
Affected products
vendor Linux Linux 24bcc89c7e7c64982e6192b4952a0a92379fc341 <3b4643ffaf72d7a5a357e9bf68b1775f8cfe7e77

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • vendor Linux Linux 24bcc89c7e7c64982e6192b4952a0a92379fc341 <3b4643ffaf72d7a5a357e9bf68b1775f8cfe7e7724bcc89c7e7c64982e6192b4952a0a92379fc341 <3b4643ffaf72d7a5a357e9bf68b1775f8cfe7e77

How to fix CVE-2025-37839

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2025-37839. EPSS is 0.33%. Act only if a listed version of Linux Linux is installed.

Which versions are affected?

Compare what you have installed with Linux Linux 24bcc89c7e7c64982e6192b4952a0a92379fc341 <3b4643ffaf72d7a5a357e9bf68b1775f8cfe7e77 24bcc89c7e7c64982e6192b4952a0a92379fc341 <3b4643ffaf72d7a5a357e9bf68b1775f8cfe7e77. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 0.33%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. 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.

  2. 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.

Sources

  • CVE.orgVulnerability recordCVE-2025-37839

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2025-37839

    30-day exploitation probability 0.3%

    first.org
  • 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

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.