CVE-2026-64360

hfs/hfsplus: zero-initialize buffer in hfs_bnode_read

MEDIUM
5.5
CVSS Score
Published: July 25, 2026 at 08:50 AM UTC
Updated: September 4, 2026 at 04:16 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.1%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 5.4.297v ≥ 6.15.11v ≥ 6.16.25.10.241 ≤ v < 5.10.2615.15.190 ≤ v < 5.15.2125.4.297 ≤ v < 5.56.1.149 ≤ v < 6.1.1786.12.43 ≤ v < 6.12.966.15.11 ≤ v < 6.166.16.2 ≤ v < 6.176.16.2 ≤ v < 6.18.396.17 ≤ v < 6.18.396.17 ≤ v < 7.1.46.17 ≤ v < 7.26.19 ≤ v < 7.1.46.6.103 ≤ v < 6.6.145384a66b89f9540a9a8cb0f48807697dfabaece4c5.10.2415.15.1905.4.2976.1.1496.12.436.15.116.16.26.176.6.10367ecc81f6492275c9c54280532f558483c99c90ea1a60e79502279f996e55052f50cc14919020475a431930c9bac518bf99d6b1da526a7f37ddee8d8e7d2dc2421e821e4045775e6dc226378328de6f6eec522fd0d28106b14a59ab2d658605febe4a3bbefc095b35b23297e419c2ab4fc1ed1a8f0781a29fc7f732984ec91f30be3e574e0644066d07f2b78fe2891a9c43ab87d1a210d61e6438ca6936e2f62
Vendor states this is fixed in 0b189b2204f1a2612dc68f8d139fb5b80539e710 (fixed)
Vendor states this is fixed in 16ca053c2be5f4f3044dccf7fc19237dc820d394 (fixed)
Vendor states this is fixed in 34684a04777358b2b40ac729e54c8e45359e46b3 (fixed)
Vendor states this is fixed in 8f72fd25a57a457866350359ddd27a43caa62c95 (fixed)
Vendor states this is fixed in d2afc7ecee476f9251dd87444f7fb6a424410922 (fixed)
Vendor states this is fixed in d5b45bad75cd2730b8452aed4d3b20a2b2a12576 (fixed)
Vendor states this is fixed in d67aadee19ffdf3cc8520c5a4f4d5b2916d30baf (fixed)
Vendor states this is fixed in f3461b84a4865d9b5e70fbb71da72ae044a3bcd2 (fixed)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Affected range stops below 5.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.96 (unaffected)
Affected range stops below 6.16, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.17 (unaffected)
Vendor states this is fixed in 6.18.39 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.4 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-908

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card