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.

Published: 2025-09-04 Last update: 2026-05-12 Assigner: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-38697 is rated Low Risk (33.5/100): CVSS High severity, with low exploitation likelihood (EPSS 0.17%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-38697

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.02% 0.17% +0.15%
2 2026-01-27 0.06% 0.02% -0.04%
3 2026-01-04 — 0.06% —

Full EPSS history (4 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-38697

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 [email protected]

Weakness enumeration for CVE-2025-38697

GitHub Security Advisory for CVE-2025-38697

GHSA-323x-vj5p-jwh3 · Severity: high — In the Linux kernel, the following vulnerability has been resolved: jfs: upper bound check of...

OS Trackers for CVE-2025-38697

vendor priority summary link
debian not yet assigned CVE-2025-38697 not yet assigned priority: Debian including 2 source packages (linux, linux-6.1), 6 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 6. https://security-tracker.debian.org/tracker/CVE-2025-38697
redhat medium — https://access.redhat.com/security/cve/CVE-2025-38697
suse high CVE-2025-38697 severity important: SUSE including 402 source package names (2.1.3-6.80:kernel-default-base-6.4.0-35.1.21.12, 2.1.3-7.57:kernel-default-6.4.0-35.1, …), 868 product×package rows across 182 product lines (Container suse/sl-micro/6.0/base-os-container, Container suse/sl-micro/6.0/kvm-os-container, … (182 product lines)): Fixed 442, Known Affected 231, Known Not Affected 195. https://www.suse.com/security/cve/CVE-2025-38697/
ubuntu medium CVE-2025-38697 medium priority: Ubuntu including 158 source packages (linux, linux-allwinner-5.19, …), 1414 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): DNE 1017, ignored 180, released 150, needed 48, not-affected 16, needs-triage 2, pending 1. https://ubuntu.com/security/CVE-2025-38697

Affected software / configurations for CVE-2025-38697

Vendor Product Version Raw CPE
linux linux_kernel >= 2.6.12.1, < 5.4.297 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 5.5, < 5.10.241 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 5.11, < 5.15.190 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 5.16, < 6.1.149 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 6.2, < 6.6.103 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 6.7, < 6.12.43 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 6.13, < 6.15.11 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 6.16, < 6.16.2 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel 2.6.12 cpe:2.3:o:linux:linux_kernel:2.6.12:-:*:*:*:*:*:*
linux linux_kernel 2.6.12 cpe:2.3:o:linux:linux_kernel:2.6.12:rc2:*:*:*:*:*:*
linux linux_kernel 2.6.12 cpe:2.3:o:linux:linux_kernel:2.6.12:rc3:*:*:*:*:*:*
linux linux_kernel 2.6.12 cpe:2.3:o:linux:linux_kernel:2.6.12:rc4:*:*:*:*:*:*
linux linux_kernel 2.6.12 cpe:2.3:o:linux:linux_kernel:2.6.12:rc5:*:*:*:*:*:*
debian debian_linux 11.0 cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*

References for CVE-2025-38697

URL Tags
https://git.kernel.org/stable/c/1467a75819e41341cd5ebd16faa2af1ca3c8f4fe Patch
https://git.kernel.org/stable/c/173cfd741ad7073640bfb7e2344c2a0ee005e769 Patch
https://git.kernel.org/stable/c/2dd05f09cc323018136a7ecdb3d1007be9ede27f Patch
https://git.kernel.org/stable/c/30e19a884c0b11f33821aacda7e72e914bec26ef Patch
https://git.kernel.org/stable/c/49ea46d9025aa1914b24ea957636cbe4367a7311 Patch
https://git.kernel.org/stable/c/5bdb9553fb134fd52ec208a8b378120670f6e784 Patch
https://git.kernel.org/stable/c/a4f199203f79ca9cd7355799ccb26800174ff093 Patch
https://git.kernel.org/stable/c/c214006856ff52a8ff17ed8da52d50601d54f9ce Patch
https://git.kernel.org/stable/c/c8ca21a2836993d7cb816668458e05e598574e55 Patch
https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html Mailing List Third Party Advisory
https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html Mailing List Third Party Advisory
https://cert-portal.siemens.com/productcert/html/ssa-032379.html
cvelogic Threat Intelligence