Security readout for executives and security teams
Plain-English summary
A flaw in Linux HFS+ filesystem handling can make the kernel read beyond allocated memory while listing extended attributes. A local, low-privileged user could potentially expose sensitive kernel data or crash the system. The supplied evidence does not show remote or active exploitation.
Executive priority
Treat as a high-priority kernel update for exposed multi-user or HFS+-processing systems. Other Linux systems can follow normal accelerated patching after confirming HFS+ exposure. There is no supplied evidence of active exploitation, but potential confidentiality and availability impact warrants timely remediation.
Technical view
hfsplus_listxattr() passed an hfsplus_attr_unistr structure to hfsplus_uni2asc(), which expected a differently sized hfsplus_unistr. An excessive Unicode length could therefore drive a slab out-of-bounds read. The fix adds structure-specific wrappers and limits the length to allocated memory. Integrity impact is not indicated.
Likely exposure
Exposure is most likely on affected Linux kernels where HFS+ filesystem support is present and HFS+ extended attributes can be accessed. Risk is greater for multi-user systems or systems processing untrusted HFS+ media. The supplied version data is incomplete or ambiguous for reliable fleet-wide version classification.
Exploitation context
The CVSS vector describes local access, low complexity, low privileges, and no user interaction. The source bundle marks KEV as false and provides no evidence of exploitation in the wild. A KASAN report from syzkaller-style testing demonstrates the faulty read, not malicious exploitation.
Researcher notes
The reported failure occurs in hfsplus_uni2asc() through the listxattr path. A previous fix, commit 94458781aee6, was insufficient because two Unicode structures have different sizes. The replacement design separates their handling and caps lengths. Exact vulnerable-to-fixed release boundaries should be verified through distribution backport records.
Mitigation direction
Install a vendor-supported kernel containing the referenced stable fix.
Prioritize multi-user systems and hosts that mount or process HFS+ filesystems.
Where operationally acceptable, restrict HFS+ use until the corrected kernel is deployed.
Consult distribution guidance for exact fixed package versions and backport status.
Validation and detection
Inventory kernel versions and compare them with distribution advisories or referenced stable commits.
Determine whether HFS+ support is enabled, loaded, or used on each system.
Identify systems mounting untrusted or user-supplied HFS+ media.
After updating, confirm the running kernel package includes the structure-specific length-limiting fix.
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-40082 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
0ADP 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.