# jbd2: remove wrong sb->s_sequence check

CVE record · `CVE-2025-37839`

- **Identifiers:** `CVE-2025-37839`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 9 May 2025
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 9 May 2025, 06:41 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `24bcc89c7e7c64982e6192b4952a0a92379fc341 to before cf30432f5b3064ff85d85639c2f0106f89c566f6` (git)
  - affected: `24bcc89c7e7c64982e6192b4952a0a92379fc341 to before b479839525fe7906966cdc4b5b2afbca048558a1` (git)
  - affected: `24bcc89c7e7c64982e6192b4952a0a92379fc341 to before ad926f735b4d4f10768fec7d080cadeb6d075cac` (git)
  - affected: `24bcc89c7e7c64982e6192b4952a0a92379fc341 to before 3b4643ffaf72d7a5a357e9bf68b1775f8cfe7e77` (git)
  - affected: `24bcc89c7e7c64982e6192b4952a0a92379fc341 to before c88f7328bb0fff66520fc9164f02b1d06e083c1b` (git)
  - affected: `24bcc89c7e7c64982e6192b4952a0a92379fc341 to before 9eaec071f111cd2124ce9a5b93536d3f6837d457` (git)
  - affected: `24bcc89c7e7c64982e6192b4952a0a92379fc341 to before c98eb9ffb1d9c98237b5e1668eee17654e129fb0` (git)
  - affected: `24bcc89c7e7c64982e6192b4952a0a92379fc341 to before b0cca357f85beb6144ab60c62dcc98508cc044bf` (git)
  - affected: `24bcc89c7e7c64982e6192b4952a0a92379fc341 to before e6eff39dd0fe4190c6146069cc16d160e71d1148` (git)
  - affected: `dd8ff32c1e7ed10fb0e168b4431983e09acbeb2f` (git)
  - affected: `3.2.71 to before 3.3` (semver)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `3.4`
  - unaffected: `before 3.4` (semver)
  - unaffected: `5.4.293 to 5.4.*, inclusive` (semver)
  - unaffected: `5.10.237 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.181 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.135 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.88 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.24 to 6.12.*, inclusive` (semver)
  - unaffected: `6.13.12 to 6.13.*, inclusive` (semver)
  - unaffected: `6.14.3 to 6.14.*, inclusive` (semver)
  - unaffected: `6.15 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The jbd2 journaling code in the Linux kernel, affected from version 3.4, has a wrong check on the superblock sequence value that can trigger a spurious kernel warning. The source gives few details about attacker access or wider impact. Upgrade to 5.4.293, 5.10.237, 5.15.181, or 6.1.135 or later in the matching series.

Written 16 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0033, the 27th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 9 May 2025, 06:41 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2025-37839)
- 9 May 2025, 07:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2025-37839)

## Sources

- [CVE List: CVE-2025-37839](https://www.cve.org/CVERecord?id=CVE-2025-37839)
- [NVD: CVE-2025-37839](https://nvd.nist.gov/vuln/detail/CVE-2025-37839)

### References from the CNA

- <https://git.kernel.org/stable/c/cf30432f5b3064ff85d85639c2f0106f89c566f6>
- <https://git.kernel.org/stable/c/b479839525fe7906966cdc4b5b2afbca048558a1>
- <https://git.kernel.org/stable/c/ad926f735b4d4f10768fec7d080cadeb6d075cac>
- <https://git.kernel.org/stable/c/3b4643ffaf72d7a5a357e9bf68b1775f8cfe7e77>
- <https://git.kernel.org/stable/c/c88f7328bb0fff66520fc9164f02b1d06e083c1b>
- <https://git.kernel.org/stable/c/9eaec071f111cd2124ce9a5b93536d3f6837d457>
- <https://git.kernel.org/stable/c/c98eb9ffb1d9c98237b5e1668eee17654e129fb0>
- <https://git.kernel.org/stable/c/b0cca357f85beb6144ab60c62dcc98508cc044bf>
- <https://git.kernel.org/stable/c/e6eff39dd0fe4190c6146069cc16d160e71d1148>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2025-37839>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2025-37839/>. Everything for agents: <https://agentprime.io/llms.txt>.
