hfs/hfsplus: zero-initialize buffer in hfs_bnode_read
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 8f72fd25a57a457866350359ddd27a43caa62c95, Kernel 6.6.145, Kernel 34684a04777358b2b40ac729e54c8e45359e46b3 and 15 more.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=fe2891a9c43ab87d1a210d61e6438ca6936e2f62 <8f72fd25a57a457866350359ddd27a43caa62c95, >=6.6.103 <6.6.145, >=67ecc81f6492275c9c54280532f558483c99c90e <34684a04777358b2b40ac729e54c8e45359e46b3, >=a1a60e79502279f996e55052f50cc14919020475 <0b189b2204f1a2612dc68f8d139fb5b80539e710, >=a431930c9bac518bf99d6b1da526a7f37ddee8d8 <d5b45bad75cd2730b8452aed4d3b20a2b2a12576, >=a431930c9bac518bf99d6b1da526a7f37ddee8d8 <d67aadee19ffdf3cc8520c5a4f4d5b2916d30baf, >=a431930c9bac518bf99d6b1da526a7f37ddee8d8 <f3461b84a4865d9b5e70fbb71da72ae044a3bcd2, >=efc095b35b23297e419c2ab4fc1ed1a8f0781a29 <d2afc7ecee476f9251dd87444f7fb6a424410922, =6.17, =e7d2dc2421e821e4045775e6dc226378328de6f6, =eec522fd0d28106b14a59ab2d658605febe4a3bb, =fc7f732984ec91f30be3e574e0644066d07f2b78, >=384a66b89f9540a9a8cb0f48807697dfabaece4c <16ca053c2be5f4f3044dccf7fc19237dc820d394, >=5.10.241 <5.10.261, >=5.15.190 <5.15.212, >=5.4.297 <5.5, >=6.1.149 <6.1.178, >=6.12.43 <6.12.96, >=6.15.11 <6.16, >=6.16.2 <6.17 | 8f72fd25a57a457866350359ddd27a43caa62c95, 6.6.145, 34684a04777358b2b40ac729e54c8e45359e46b3, 0b189b2204f1a2612dc68f8d139fb5b80539e710, d5b45bad75cd2730b8452aed4d3b20a2b2a12576, d67aadee19ffdf3cc8520c5a4f4d5b2916d30baf, f3461b84a4865d9b5e70fbb71da72ae044a3bcd2, d2afc7ecee476f9251dd87444f7fb6a424410922, 16ca053c2be5f4f3044dccf7fc19237dc820d394, 5.10.261, 5.15.212, 5.5, 6.1.178, 6.12.96, 6.16, 6.17 |
| linux-kernel: Kernel | >=5.11.0 <5.15.212, >=5.16.0 <6.1.178, >=6.13.0 <6.18.39, >=6.17.0 <7.1.4, >=6.2.0 <6.6.145, >=6.7.0 <6.12.96, <5.10.261 | 5.15.212, 6.1.178, 6.18.39, 7.1.4, 6.6.145, 6.12.96, 5.10.261 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket