CVE-2024-40902: jfs: xattr: fix buffer overflow for invalid xattr
In the Linux kernel, the following vulnerability has been resolved:
jfs: xattr: fix buffer overflow for invalid xattr
When an xattr size is not what is expected, it is printed out to the
kernel log in hex format as a form of debugging. But when that xattr
size is bigger than the expected size, printing it out can cause an
access off the end of the buffer.
Fix this all up by properly restricting the size of the debug hex dump
in the kernel log.
Security readout for executives and security teams
Plain-English summary
A flaw in Linux’s JFS filesystem can make the kernel read beyond a buffer while logging an abnormally sized extended attribute. The supplied CVSS score is 7.8, reflecting potentially serious local impact. Exposure is concentrated on systems that use JFS and allow a low-privileged user to reach the affected operation.
Executive priority
Treat this as a high-priority kernel maintenance issue on JFS-dependent systems, especially multi-user hosts where low-privileged users can reach filesystem operations. Use normal emergency patch governance rather than assuming internet-wide exposure. Confirm distribution-specific fixes promptly because upstream version strings alone may not show backports.
Technical view
CVE-2024-40902 is an out-of-bounds buffer access in JFS extended-attribute diagnostic logging. An unexpected xattr size could cause the hexadecimal debug dump to access beyond the buffer. The kernel fix restricts the dump length. The supplied assessment classifies access as local, low-complexity, and requiring low privileges, without user interaction.
Likely exposure
Likely exposure is limited to Linux systems running an affected kernel and using or processing JFS filesystems. The supplied version data spans multiple kernel branches but does not map every distribution build. Systems without JFS use are less likely to reach the vulnerable code, though kernel and filesystem inventories are needed for confirmation.
Exploitation context
The supplied record does not identify active exploitation, and the CVE is not listed as KEV in the bundle. No public proof-of-concept or confirmed attack evidence is provided. The CVSS vector describes local access requiring low privileges, so this should not be presented as a directly remote vulnerability.
Researcher notes
The record assigns CWE-121 and CVSS 3.1 score 7.8. The described defect is an over-read during debug hex dumping of an invalid JFS xattr, corrected by bounding the dump size. The sources do not establish exploitability beyond the CVSS impact assessment, so confidentiality, integrity, or code-execution outcomes should not be claimed as demonstrated.
Mitigation direction
Install the distribution-supported kernel update containing the applicable stable JFS fix.
Prioritize systems that mount, process, or permit user access to JFS filesystems.
Consult the Linux distribution’s advisory for exact fixed package versions.
If updates are delayed, follow vendor guidance for reducing JFS exposure; no sourced workaround is provided.
Validation and detection
Inventory kernel package versions across Linux hosts.
Identify hosts with JFS support, mounts, images, or operational dependencies.
Map each distribution kernel build to its vendor advisory or applicable stable fix.
After updating, verify the running kernel changed and reboot requirements were completed.
Confirm security scanners recognize the distribution’s backported fix, not only upstream version numbers.
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-121: 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-121 · source CWE mapping
Stack-based Buffer Overflow
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.