CVE-2025-38715: hfs: fix slab-out-of-bounds in hfs_bnode_read()
In the Linux kernel, the following vulnerability has been resolved:
hfs: fix slab-out-of-bounds in hfs_bnode_read()
This patch introduces is_bnode_offset_valid() method that checks
the requested offset value. Also, it introduces
check_and_correct_requested_length() method that checks and
correct the requested length (if it is necessary). These methods
are used in hfs_bnode_read(), hfs_bnode_write(), hfs_bnode_clear(),
hfs_bnode_copy(), and hfs_bnode_move() with the goal to prevent
the access out of allocated memory and triggering the crash.
Security readout for executives and security teams
Plain-English summary
A Linux HFS filesystem flaw can access memory outside an allocated kernel object when processing invalid offsets or lengths. The source explicitly identifies kernel crashes; its CVSS assessment also indicates possible confidentiality, integrity, and availability impact. Exploitation requires local, low-privileged access and no user interaction.
Executive priority
Treat this as a high-priority kernel update, especially for multi-user systems or environments using HFS. It is not presented as an internet-wide emergency because access is local and active exploitation is unconfirmed. Accelerate remediation where untrusted users or workloads can reach HFS functionality.
Technical view
The flaw is a slab-out-of-bounds condition in HFS b-node handling. The kernel fix validates requested offsets and corrects unsafe lengths across hfs_bnode_read(), write(), clear(), copy(), and move(). It is rated CVSS 3.1 7.8 with local access, low complexity, low privileges, and high potential impact.
Likely exposure
Exposure is concentrated on Linux systems running affected kernels where HFS filesystem functionality is enabled, loadable, or used. Multi-user systems and workflows handling HFS media deserve priority. Systems that do not use HFS may have lower practical exposure, but configuration and vendor package status must be verified.
Exploitation context
The supplied record is not in CISA KEV and provides no evidence of active exploitation or a public exploit. The CVSS vector describes a local, low-privileged attack without user interaction, not an unauthenticated remote compromise. The precise path for reaching vulnerable HFS operations is not documented in the supplied description.
Researcher notes
Version metadata mixes a foundational commit hash with release values and may not represent vendor backports cleanly. Validate exposure using vendor advisories and referenced stable commits. The description explicitly supports out-of-bounds access and crashes; broader confidentiality and integrity consequences come from the supplied CVSS vector rather than a documented exploitation outcome.
Mitigation direction
Apply vendor-supported kernel updates containing the HFS offset and length validation fixes.
Prioritize systems using HFS or permitting low-privileged local access.
Follow distribution or appliance guidance for exact fixed package versions and update activation requirements.
If patching is delayed, reduce unnecessary HFS exposure according to vendor guidance.
Validation and detection
Inventory running kernel versions and vendor kernel packages across Linux assets.
Determine whether HFS support is enabled, loadable, or used in operational workflows.
Confirm deployed source or vendor packages incorporate a referenced stable kernel fix.
After updating, verify the active kernel is the vendor-fixed version.
Monitor affected systems for HFS-related kernel crashes 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.
cve · low confidence lookup
CVE-2025-38715 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
2ADP providers
13Source 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.