CyberRota Analysis
AI-GeneratedThe vulnerability affects the Linux kernel's handling of buffer initialization in the hfs_bnode_read function, where early returns can lead to the use of uninitialized stack-allocated buffers. This can result in potential information leakage or undefined behavior, particularly when the output is used unconditionally by callers. Organizations using Linux systems, especially those relying on HFS/HFS+ file systems, should prioritize addressing this issue to mitigate risks associated with uninitialized memory access.
Original NVD 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.