CVE-2025-37839

jbd2: remove wrong sb->s_sequence check

HIGH

7.8

CVSS Score

Published: May 9, 2025 at 06:41 AM UTC

Updated: June 17, 2026 at 09:15 AM UTC

2 products affected across 2 vendorsLinux KernelDebian Linux

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

HIGH7.8

Exploit prediction

EPSS 0.3%

Description

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Debian Linux · Debiandrupal

95%

11.0

Linux Kernel · Linux

95%

v ≥ 3.2.71v < 5.4.2933.2.71 ≤ v < 3.33.4 ≤ v < 5.10.2373.4 ≤ v < 5.15.1813.4 ≤ v < 5.4.2933.4 ≤ v < 6.1.1353.4 ≤ v < 6.12.243.4 ≤ v < 6.13.123.4 ≤ v < 6.14.33.4 ≤ v < 6.153.4 ≤ v < 6.6.885.11 ≤ v < 5.15.1815.16 ≤ v < 6.1.1355.5 ≤ v < 5.10.2376.13 ≤ v < 6.13.126.14 ≤ v < 6.14.36.2 ≤ v < 6.6.886.7 ≤ v < 6.12.2424bcc89c7e7c64982e6192b4952a0a92379fc3413.2.71 3.4dd8ff32c1e7ed10fb0e168b4431983e09acbeb2f

Vendor states this is fixed in 3b4643ffaf72d7a5a357e9bf68b1775f8cfe7e77 (fixed)

Vendor states this is fixed in 9eaec071f111cd2124ce9a5b93536d3f6837d457 (fixed)

Vendor states this is fixed in ad926f735b4d4f10768fec7d080cadeb6d075cac (fixed)

Vendor states this is fixed in b0cca357f85beb6144ab60c62dcc98508cc044bf (fixed)

Vendor states this is fixed in b479839525fe7906966cdc4b5b2afbca048558a1 (fixed)

Vendor states this is fixed in c88f7328bb0fff66520fc9164f02b1d06e083c1b (fixed)

Vendor states this is fixed in c98eb9ffb1d9c98237b5e1668eee17654e129fb0 (fixed)

Vendor states this is fixed in cf30432f5b3064ff85d85639c2f0106f89c566f6 (fixed)

Vendor states this is fixed in e6eff39dd0fe4190c6146069cc16d160e71d1148 (fixed)

Affected range stops below 3.3, so it looks safe — our inference, not a vendor statement

Vendor states this is fixed in 3.4 (unaffected)

Vendor states this is fixed in 5.10.237 (unaffected)

Vendor states this is fixed in 5.15.181 (unaffected)

Vendor states this is fixed in 5.4.293 (unaffected)

Vendor states this is fixed in 6.1.135 (unaffected)

Vendor states this is fixed in 6.12.24 (unaffected)

Vendor states this is fixed in 6.13.12 (unaffected)

Vendor states this is fixed in 6.14.3 (unaffected)

Vendor states this is fixed in 6.15 (unaffected)

Vendor states this is fixed in 6.6.88 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references