CVE-2025-37839
jbd2: remove wrong sb->s_sequence check
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 3.2.71 · fixed in 3.3
- Linux Linux
3.4
References 9
git.kernel.org
- stable/c/cf30432f5b3064ff85d85639c2f0106f89c566f6
- stable/c/b479839525fe7906966cdc4b5b2afbca048558a1
- stable/c/ad926f735b4d4f10768fec7d080cadeb6d075cac
- stable/c/3b4643ffaf72d7a5a357e9bf68b1775f8cfe7e77
- stable/c/c88f7328bb0fff66520fc9164f02b1d06e083c1b
- stable/c/9eaec071f111cd2124ce9a5b93536d3f6837d457
- stable/c/c98eb9ffb1d9c98237b5e1668eee17654e129fb0
- stable/c/b0cca357f85beb6144ab60c62dcc98508cc044bf
- stable/c/e6eff39dd0fe4190c6146069cc16d160e71d1148