Tracker / CVE-2025-37839
CVE-2025-37839
High 7.8
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 products and versions
| debian | debian_linux |
|---|---|
| linux | linux_kernel · … → 5.4.293 |
| linux | linux_kernel · 5.11 → 5.15.181 |
| linux | linux_kernel · 5.16 → 6.1.135 |
| linux | linux_kernel · 5.5 → 5.10.237 |
| linux | linux_kernel · 6.13 → 6.13.12 |
| linux | linux_kernel · 6.14 → 6.14.3 |
| linux | linux_kernel · 6.2 → 6.6.88 |
| linux | linux_kernel · 6.7 → 6.12.24 |
Analysis
This page is not indexable yet.Until it carries original analysis — what it actually exposes, how to check in two minutes whether a system was touched, what to do if it was — the page stays noindex. The database decides that, not the template.