CVE-2024-56596: jfs: fix array-index-out-of-bounds in jfs_readdir
In the Linux kernel, the following vulnerability has been resolved:
jfs: fix array-index-out-of-bounds in jfs_readdir
The stbl might contain some invalid values. Added a check to
return error code in that case.
Security readout for executives and security teams
Plain-English summary
A flaw in Linux’s JFS filesystem directory-reading code can access memory outside an intended array when filesystem metadata contains invalid values. Triggering requires local interaction with affected JFS content, but the supplied CVSS assessment indicates potentially serious confidentiality, integrity, and availability impact.
Executive priority
Prioritize affected systems that mount JFS or process externally supplied filesystem images. Treat internet-facing systems without JFS usage as lower practical urgency, while still applying normal kernel maintenance. Because version information in the supplied bundle is not sufficiently clear for package-level decisions, require vendor confirmation before closing remediation.
Technical view
CVE-2024-56596 is a CWE-129 array-index validation flaw in jfs_readdir. Invalid stbl entries can cause an out-of-bounds array access. The upstream correction validates these values and returns an error when they are invalid. The supplied data rates it CVSS 3.1 7.8 with local access, low complexity, no privileges, and user interaction.
Likely exposure
Exposure is most likely on systems running an affected Linux kernel where JFS is enabled and JFS directory data can be processed. Systems that never use JFS have substantially reduced practical exposure. The supplied version listing is ambiguous, so distribution-specific kernel status should be verified.
Exploitation context
The CVSS vector describes a local, low-complexity condition requiring user interaction but no privileges. The supplied sources do not establish a reliable exploitation method, public weaponization, or active exploitation. This CVE is not identified as present in KEV.
Researcher notes
The evidence establishes an out-of-bounds index caused by invalid stbl values in jfs_readdir and a validation-based upstream fix. It does not establish exploitability beyond the CVSS assessment or document observed attacks. Researchers should distinguish code presence from reachability through an enabled, mounted, or processed JFS filesystem.
Mitigation direction
Install the vendor-supported kernel update that includes the applicable upstream JFS correction.
Check Linux distribution advisories for the exact fixed package version.
Where operationally acceptable, avoid mounting or processing untrusted JFS filesystems until updated.
Restrict untrusted users and workflows from introducing JFS images or media.
Validation and detection
Inventory kernel versions and determine which systems enable or use JFS.
Compare installed kernel packages with distribution advisories and upstream stable fixes.
Confirm updated systems booted into the corrected kernel, not an older installed kernel.
Review filesystem mounts and image-processing workflows for exposure to untrusted JFS content.
Monitor kernel logs for JFS errors or memory-safety reports.
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.
cwe · low confidence lookup
CWE-129: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
2CVSS vectors
3Timeline events
2ADP providers
10Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
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.