Vulnerability · CVE-2025-38697
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
Published Sep 4, 2025 · catalog updated Oct 19, 2026 · Linux Linux
Check this week
CVE-2025-38697 is not in CISA KEV. FIRST estimates a 18.00% chance of exploitation in the next 30 days. Check whether you run Linux Linux.
Gaps on this record
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- High7.8
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 18.00%
- Remediation
- Version ranges on file
- Affected products
- cpe debian/debian linux · cpe linux/linux kernel · vendor Linux Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c8ca21a2836993d7cb816668458e05e598574e55
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.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- cpe debian/debian linux11.0
- cpe linux/linux kernelversion unspecified
- vendor Linux Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c8ca21a2836993d7cb816668458e05e598574e551da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c8ca21a2836993d7cb816668458e05e598574e55
How to fix CVE-2025-38697
Recommended remediation
Affected version ranges suggest a fixed boundary. Verify against the vendor advisory for your release.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
CVE-2025-38697 is not in CISA KEV. FIRST estimates a 18.00% chance of exploitation in the next 30 days. Check whether you run Linux Linux.
Which versions are affected?
Compare what you have installed with debian/debian linux 11.0; Linux Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c8ca21a2836993d7cb816668458e05e598574e55 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c8ca21a2836993d7cb816668458e05e598574e55. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-129: Improper Validation of Array Index. EPSS 18.00%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Sep 4, 2025 · NIST NVD
Detected
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.
Oct 19, 2026 · NIST NVD
Updated
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.
Sources
- CVE.orgVulnerability recordCVE-2025-38697
Official CVE identifier
cve.org - EUVDVulnerability recordEUVD-2025-26772
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 f
euvd.enisa.europa.eu - NIST NVDVulnerability recordCVE-2025-38697
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
nvd.nist.gov
References
Freshness
Last verified in this catalog Oct 19, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.