CVE-2025-38204: jfs: fix array-index-out-of-bounds read in add_missing_indices
In the Linux kernel, the following vulnerability has been resolved:
jfs: fix array-index-out-of-bounds read in add_missing_indices
stbl is s8 but it must contain offsets into slot which can go from 0 to
127.
Added a bound check for that error and return -EIO if the check fails.
Also make jfs_readdir return with error if add_missing_indices returns
with an error.
Security readout for executives and security teams
Plain-English summary
A flaw in the Linux JFS filesystem can make the kernel read beyond an array while listing a directory. Triggering it requires local interaction with affected JFS data; it is not described as remotely exploitable. The supplied CVSS assessment is 7.8 and indicates potentially serious confidentiality, integrity, and availability consequences, although the sources do not detail specific outcomes.
Executive priority
Prioritize affected systems that actively use JFS or handle externally supplied filesystem data. Remediate through normal high-severity kernel patching, accelerating exposed or high-value hosts. Broad emergency action is not supported by the supplied evidence because active exploitation is not reported and triggering is characterized as local with user interaction.
Technical view
In JFS add_missing_indices, an s8 value stores offsets into a slot array whose valid offsets can reach 127. Invalid signed values can cause an out-of-bounds read. The correction validates the offset, returns -EIO on failure, and makes jfs_readdir propagate that error. The bundle identifies stable-kernel correction commits but provides ambiguous affected-version formatting.
Likely exposure
Exposure is most likely where an affected Linux kernel has JFS available and processes a triggering JFS directory state. Systems that do not use or permit JFS have substantially reduced practical exposure. Confirm distribution-specific status because the supplied version list does not clearly express fixed-versus-vulnerable ranges.
Exploitation context
The CVSS vector characterizes exploitation as local, low complexity, requiring no privileges but requiring user interaction. The bundle marks KEV false and provides no evidence of active exploitation, public weaponization, or remote reachability. Treat claims beyond those facts as unconfirmed.
Researcher notes
The root issue is an out-of-bounds read caused by representing slot offsets with signed 8-bit storage. The patch adds bounds validation and error propagation through jfs_readdir. The supplied CVSS claims high impact across all three security properties, but the bundle does not document a demonstrated crash, disclosure, corruption primitive, or code-execution path.
Mitigation direction
Install a supported vendor kernel update that incorporates the cited JFS correction.
Consult the Linux distribution's advisory for package-specific fixed versions.
Avoid processing untrusted JFS filesystems until the corrected kernel is running.
Reboot into the updated kernel when required by the distribution.
Validation and detection
Inventory running kernel versions and associated distribution package builds.
Determine whether JFS is enabled, mounted, or operationally required.
Match vendor changelogs against CVE-2025-38204 or the cited stable commits.
After updating, confirm every system is running the corrected kernel.
Reassess JFS usage and document systems awaiting remediation.
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-38204 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
1ADP providers
7Source 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.