CVE-2025-37839
Linux Kernel jbd2 Journal Corruption Information Disclosure
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.
INFO
Published Date :
May 9, 2025, 7:16 a.m.
Last Modified :
May 12, 2025, 5:32 p.m.
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Remotely Exploitable :
No
Impact Score :
Exploitability Score :
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2025-37839.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2025-37839 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2025-37839 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 09, 2025
Action Type Old Value New Value Added 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. Added Reference https://git.kernel.org/stable/c/3b4643ffaf72d7a5a357e9bf68b1775f8cfe7e77 Added Reference https://git.kernel.org/stable/c/9eaec071f111cd2124ce9a5b93536d3f6837d457 Added Reference https://git.kernel.org/stable/c/ad926f735b4d4f10768fec7d080cadeb6d075cac Added Reference https://git.kernel.org/stable/c/b0cca357f85beb6144ab60c62dcc98508cc044bf Added Reference https://git.kernel.org/stable/c/b479839525fe7906966cdc4b5b2afbca048558a1 Added Reference https://git.kernel.org/stable/c/c88f7328bb0fff66520fc9164f02b1d06e083c1b Added Reference https://git.kernel.org/stable/c/c98eb9ffb1d9c98237b5e1668eee17654e129fb0 Added Reference https://git.kernel.org/stable/c/cf30432f5b3064ff85d85639c2f0106f89c566f6 Added Reference https://git.kernel.org/stable/c/e6eff39dd0fe4190c6146069cc16d160e71d1148
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2025-37839 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2025-37839
weaknesses.