CVE-2026-64360
In the Linux kernel, the following vulnerability has been resolved:
hfs/hfsplus: zero-initialize buffer in hfs_bnode_read
hfs_bnode_read() can return early without writing to the output buffer
when is_bnode_offset_valid() fails or when check_and_correct_requested_
length() corrects the length to zero. Callers such as hfs_bnode_read_
u16() and hfs_bnode_read_u8() pass stack-allocated buffers and use the
result unconditionally, leading to KMSAN uninit-value reports.
Rather than initializing at each individual call site, zero the buffer
at the start of hfs_bnode_read() before any validation checks. This
ensures all callers in both hfs and hfsplus get a deterministic zero
value regardless of which early-return path is taken.
CSIRTS triage
- What
- There is a zero-initialize buffer issue in the hfs_bnode_read function of the hfs/hfsplus driver.
- Who is affected
- Deployments using the hfs/hfsplus driver are affected.
- Urgency
- Remediation urgency is unclear due to unknown severity and no exploitation reported.
- Action
- Monitor for updates regarding this issue.
AI-assisted analysis generated from the source advisory — verify against the original.
⚡ Watch CVE-2026-64360
Get an email if CVE-2026-64360 is added to CISA KEV, gains public exploit code, or a new advisory cites it — max one per day, one-click unsubscribe.
Exploitation outlook
- Low exploitation risk0.18% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 7% of all EPSS-scored CVEs.
Advisory coverage (2)
- unknownCVE-2026-64360: In the Linux kernel, the following vulnerability has been resolved: hfs/hfsplus: zero-initiali…nvd · 2026-07-25
- mediumCVE-2026-64360: hfs/hfsplus: zero-initialize buffer in hfs_bnode_readmsrc · 2026-07-14
External references
Embed the live status
— this badge updates automatically when the KEV or exploit status changes. How to embed it →
[](https://www.csirts.com/cve/CVE-2026-64360)