jbd2: remove wrong sb->s_sequence check
3Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackepss 0.3%
exploitation probability
0.3%top 76% of all CVEs
observed exploitation
nono source reports it
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
Linux · LinuxReferences
https://git.kernel.org/stable/c/3b4643ffaf72d7a5a357e9bf68b1775f8cfe7e77https://git.kernel.org/stable/c/9eaec071f111cd2124ce9a5b93536d3f6837d457https://git.kernel.org/stable/c/ad926f735b4d4f10768fec7d080cadeb6d075cachttps://git.kernel.org/stable/c/b0cca357f85beb6144ab60c62dcc98508cc044bfhttps://git.kernel.org/stable/c/b479839525fe7906966cdc4b5b2afbca048558a1https://git.kernel.org/stable/c/c88f7328bb0fff66520fc9164f02b1d06e083c1bhttps://git.kernel.org/stable/c/c98eb9ffb1d9c98237b5e1668eee17654e129fb0https://git.kernel.org/stable/c/cf30432f5b3064ff85d85639c2f0106f89c566f6https://git.kernel.org/stable/c/e6eff39dd0fe4190c6146069cc16d160e71d1148https://lists.debian.org/debian-lts-announce/2025/05/msg00030.htmlhttps://lists.debian.org/debian-lts-announce/2025/05/msg00045.html