Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-38697

jfs: upper bound check of tree index in dbAllocAG

Description

In the Linux kernel, the following vulnerability has been resolved: jfs: upper bound check of tree index in dbAllocAG When computing the tree index in dbAllocAG, we never check if we are out of bounds realative to the size of the stree. This could happen in a scenario where the filesystem metadata are corrupted.

Timeline

  1. ID reserved

    By Linux

  2. · 5 months later

    Published

  3. · 11 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-38697, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.19% · top 91% of all CVEs (11 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 5bdb9553fb134fd52ec208a8b378120670f6e784
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < a4f199203f79ca9cd7355799ccb26800174ff093
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 1467a75819e41341cd5ebd16faa2af1ca3c8f4fe
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 49ea46d9025aa1914b24ea957636cbe4367a7311
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 173cfd741ad7073640bfb7e2344c2a0ee005e769
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < c8ca21a2836993d7cb816668458e05e598574e55
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 2dd05f09cc323018136a7ecdb3d1007be9ede27f
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 30e19a884c0b11f33821aacda7e72e914bec26ef
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < c214006856ff52a8ff17ed8da52d50601d54f9ce
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 5.4.297 – ≤ 5.4.*
    • unaffected 5.10.241 – ≤ 5.10.*
    • unaffected 5.15.190 – ≤ 5.15.*
    • unaffected 6.1.149 – ≤ 6.1.*
    • unaffected 6.6.103 – ≤ 6.6.*
    • unaffected 6.12.43 – ≤ 6.12.*
    • unaffected 6.15.11 – ≤ 6.15.*
    • unaffected 6.16.2 – ≤ 6.16.*
    • unaffected 6.17 – ≤ *

References

References12

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-38697 badge
[![CVE-2025-38697](https://cveledger.app/badge/CVE-2025-38697.svg)](https://cveledger.app/cve/CVE-2025-38697)

Record last updated .