Bug 2507058 (CVE-2026-64360) - CVE-2026-64360 kernel: hfs/hfsplus: zero-initialize buffer in hfs_bnode_read
Summary: CVE-2026-64360 kernel: hfs/hfsplus: zero-initialize buffer in hfs_bnode_read
Keywords:
Status: NEW
Alias: CVE-2026-64360
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-07-25 10:02 UTC by OSIDB Bzimport
Modified: 2026-07-29 22:10 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-07-25 10:02:50 UTC
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.

Comment 1 Mauro Matteo Cascella 2026-07-29 22:03:40 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2026072520-CVE-2026-64360-402f@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.