Kernel warning via valid zero transaction ID
Published May 9, 2025 · Updated May 23, 2026
An incorrect assertion in Linux kernel jbd2 allows local users to trigger a kernel warning when a valid journal transaction ID is zero. The jbd2_journal_update_sb_log_tail function tests sb->s_sequence even though sb->s_start determines journal emptiness and zero is a valid sequence value. A local journal-tail update with sequence zero reaches WARN_ON; service interruption is limited to systems configured to panic on kernel warnings.
Summary
What happened
An incorrect assertion in Linux kernel jbd2 allows local users to trigger a kernel warning when a valid journal transaction ID is zero. The jbd2_journal_update_sb_log_tail function tests sb->s_sequence even though sb->s_start determines journal emptiness and zero is a valid sequence value. A local journal-tail update with sequence zero reaches WARN_ON; service interruption is limited to systems configured to panic on kernel warnings.
The record
- CVE
- CVE-2025-37839
- Published
- May 9, 2025
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 9, 2025CVE publishedPublication date reported by the CVE source.
- May 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=24bcc89c7e7c64982e6192b4952a0a92379fc341 <3b4643ffaf72d7a5a357e9bf68b1775f8cfe7e77
- Affected versionversion=24bcc89c7e7c64982e6192b4952a0a92379fc341 <9eaec071f111cd2124ce9a5b93536d3f6837d457
- Affected versionversion=24bcc89c7e7c64982e6192b4952a0a92379fc341 <ad926f735b4d4f10768fec7d080cadeb6d075cac
- Affected versionversion=24bcc89c7e7c64982e6192b4952a0a92379fc341 <b0cca357f85beb6144ab60c62dcc98508cc044bf
- Affected versionversion=24bcc89c7e7c64982e6192b4952a0a92379fc341 <b479839525fe7906966cdc4b5b2afbca048558a1
- Affected versionversion=24bcc89c7e7c64982e6192b4952a0a92379fc341 <c88f7328bb0fff66520fc9164f02b1d06e083c1b
- Affected versionversion=24bcc89c7e7c64982e6192b4952a0a92379fc341 <c98eb9ffb1d9c98237b5e1668eee17654e129fb0
- Affected versionversion=24bcc89c7e7c64982e6192b4952a0a92379fc341 <cf30432f5b3064ff85d85639c2f0106f89c566f6
- Affected versionversion=24bcc89c7e7c64982e6192b4952a0a92379fc341 <e6eff39dd0fe4190c6146069cc16d160e71d1148
- Affected versionversion=3.2.71 <3.3
- Affected versionversion=3.4
- Affected versionversion=dd8ff32c1e7ed10fb0e168b4431983e09acbeb2f
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo