Answer in brief
CVE-2025-37839 records a High severity (CVSS 7.8) vulnerability in jbd2: remove wrong sb->s_sequence check. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=24bcc89c7e7c64982e6192b4952a0a92379fc341 <cf30432f5b3064ff85d85639c2f0106f89c566f6 || >=24bcc89c7e7c64982e6192b4952a0a92379fc341 <b479839525fe7906966cdc4b5b2afbca048558a1 || >=24bcc89c7e7c64982e6192b4952a0a92379fc341 <ad926f735b4d4f10768fec7d080cadeb6d075cac || >=24bcc89c7e7c64982e6192b4952a0a92379fc341 <3b4643ffaf72d7a5a357e9bf68b1775f8cfe7e77 || >=24bcc89c7e7c64982e6192b4952a0a92379fc341 <c88f7328bb0fff66520fc9164f02b1d06e083c1b || >=24bcc89c7e7c64982e6192b4952a0a92379fc341 <9eaec071f111cd2124ce9a5b93536d3f6837d457 || >=24bcc89c7e7c64982e6192b4952a0a92379fc341 <c98eb9ffb1d9c98237b5e1668eee17654e129fb0 || >=24bcc89c7e7c64982e6192b4952a0a92379fc341 <b0cca357f85beb6144ab60c62dcc98508cc044bf || >=24bcc89c7e7c64982e6192b4952a0a92379fc341 <e6eff39dd0fe4190c6146069cc16d160e71d1148 || dd8ff32c1e7ed10fb0e168b4431983e09acbeb2f || >=3.2.71 <3.3 | cf30432f5b3064ff85d85639c2f0106f89c566f6, b479839525fe7906966cdc4b5b2afbca048558a1, ad926f735b4d4f10768fec7d080cadeb6d075cac, 3b4643ffaf72d7a5a357e9bf68b1775f8cfe7e77, c88f7328bb0fff66520fc9164f02b1d06e083c1b, 9eaec071f111cd2124ce9a5b93536d3f6837d457, c98eb9ffb1d9c98237b5e1668eee17654e129fb0, b0cca357f85beb6144ab60c62dcc98508cc044bf, e6eff39dd0fe4190c6146069cc16d160e71d1148, 3.3 |
| Linux/Linuxgeneric | 3.4 | Not reported |
Published upstream
May 9, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.