CVE-2025-38697: jfs: upper bound check of tree index in dbAllocAG
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.
Security readout for executives and security teams
Plain-English summary
A flaw in Linux's JFS filesystem code can use an invalid tree index when filesystem metadata is corrupted. Successful triggering could compromise confidentiality, integrity, and availability. The issue requires local access and applies primarily where JFS is enabled or used.
Executive priority
Treat as a high-priority kernel maintenance issue where JFS is used, particularly on multi-user systems or systems handling external storage. Patch through normal emergency or accelerated maintenance. Lower the priority only after confirming JFS is neither enabled nor reachable.
Technical view
CVE-2025-38697 affects dbAllocAG in the Linux JFS implementation. A computed tree index was not checked against the stree upper bound, allowing out-of-bounds behavior when processing corrupted filesystem metadata. The supplied CVSS 3.1 score is 7.8 with local, low-complexity, low-privilege attack conditions and high impacts.
Likely exposure
Prioritize Linux systems that run an affected kernel and mount or process JFS filesystems, especially untrusted or potentially corrupted volumes. Systems without JFS use are less likely to reach the vulnerable path. The supplied version data is complex, so confirm exposure against distribution or vendor advisories.
Exploitation context
The source bundle does not establish active exploitation, and the CVE is not listed as KEV. The CVSS vector indicates local access and low privileges, while the description identifies corrupted filesystem metadata as the triggering condition. Public sources supplied here do not clarify reliable exploitability beyond that condition.
Researcher notes
The defect is an absent upper-bound check for the tree index computed by dbAllocAG relative to stree size. Corrupted metadata can drive the index out of bounds. The supplied material does not identify a CWE, observed exploitation, public proof of concept, or precise consequences demonstrated in practice.
Mitigation direction
Install a vendor-supported kernel containing the cited JFS bounds-check fix.
Follow Linux distribution or appliance-vendor advisories for the correct fixed package.
Restrict mounting or processing of untrusted JFS volumes until patched.
Reduce JFS use where it is unnecessary and operationally safe to do so.
Validation and detection
Inventory kernel versions and identify systems where JFS is enabled or mounted.
Compare installed kernel packages with current distribution or vendor advisories.
Confirm the deployed kernel includes the applicable cited stable-tree fix.
Review storage workflows for untrusted or corrupted JFS images and media.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-38697 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
2ADP providers
13Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.