CVE-2025-37839Published May 9, 2025 · May 9Updated 3d ago
jbd2: remove wrong sb->s_sequence check
Linux
High7.8Fix available
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 24bcc89c7e7c64982e6192b4952a0a92379fc341 · < 9eaec071f111cd2124ce9a5b93536d3f6837d457| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The jbd2 component of the Linux kernel incorrectly checks whether a journal is empty using a transaction ID that can validly be zero. This can spuriously trigger a kernel warning; the input does not specify attacker capabilities, access requirements, or user interaction.
Engineers running the Linux kernel should check their installations; affected versions are not specified.