CVE-2026-64360
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Weakness
- CWE-908
- Record status
- Analyzed
Affected
- Linux Kernel < 5.5
- Linux Kernel < 5.10.261
- Linux Kernel < 5.15.212
- Linux Kernel < 6.1.178
- Linux Kernel < 6.6.145
- Linux Kernel < 6.12.96
- Linux Kernel < 6.16
- Linux Kernel < 6.18.39
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-64360.md and follow it. Check whether this project is affected by CVE-2026-64360. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/0b189b2204f1a2612dc68f8d139fb5b80539e710
- https://git.kernel.org/stable/c/16ca053c2be5f4f3044dccf7fc19237dc820d394
- https://git.kernel.org/stable/c/34684a04777358b2b40ac729e54c8e45359e46b3
- https://git.kernel.org/stable/c/8f72fd25a57a457866350359ddd27a43caa62c95
- https://git.kernel.org/stable/c/d2afc7ecee476f9251dd87444f7fb6a424410922
- https://git.kernel.org/stable/c/d5b45bad75cd2730b8452aed4d3b20a2b2a12576
- https://git.kernel.org/stable/c/d67aadee19ffdf3cc8520c5a4f4d5b2916d30baf
- https://git.kernel.org/stable/c/f3461b84a4865d9b5e70fbb71da72ae044a3bcd2
References
- https://git.kernel.org/stable/c/0b189b2204f1a2612dc68f8d139fb5b80539e710
- https://git.kernel.org/stable/c/16ca053c2be5f4f3044dccf7fc19237dc820d394
- https://git.kernel.org/stable/c/34684a04777358b2b40ac729e54c8e45359e46b3
- https://git.kernel.org/stable/c/8f72fd25a57a457866350359ddd27a43caa62c95
- https://git.kernel.org/stable/c/d2afc7ecee476f9251dd87444f7fb6a424410922
- https://git.kernel.org/stable/c/d5b45bad75cd2730b8452aed4d3b20a2b2a12576
- https://git.kernel.org/stable/c/d67aadee19ffdf3cc8520c5a4f4d5b2916d30baf
- https://git.kernel.org/stable/c/f3461b84a4865d9b5e70fbb71da72ae044a3bcd2