CVE-2026-64360
Last modified
CVE-2026-64360 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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. EPSS estimates a 0.18% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 5.4.297, < 5.5 |
| Linux | Linux Kernel | >= 5.10.241, < 5.10.261 |
| Linux | Linux Kernel | >= 5.15.190, < 5.15.212 |
| Linux | Linux Kernel | >= 6.1.149, < 6.1.178 |
| Linux | Linux Kernel | >= 6.6.103, < 6.6.145 |
| Linux | Linux Kernel | >= 6.12.43, < 6.12.96 |
| Linux | Linux Kernel | >= 6.15.11, < 6.16 |
| Linux | Linux Kernel | >= 6.16.2, < 6.18.39 |
| Linux | Linux Kernel | >= 6.19, < 7.1.4 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-64360?
How severe is CVE-2026-64360?
How do I fix CVE-2026-64360?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64354In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64355In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-64356In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64357In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64358In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64359In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64361In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64362In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64363In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64364In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-64365In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64366In the Linux kernel, the following vulnerability has been re…8.8
Are you affected by CVE-2026-64360?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
