Nixpkgs security tracker

Login with GitHub

Suggestion detail

Dismissed
(max. allowed matches exceeded)
created 5 hours ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
hfs/hfsplus: zero-initialize buffer in hfs_bnode_read

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 products

Linux
  • <5.10.261
  • <d5b45bad75cd2730b8452aed4d3b20a2b2a12576
  • ==6.17
  • <6.16
  • <0b189b2204f1a2612dc68f8d139fb5b80539e710
  • =<7.1.*
  • =<6.1.*
  • =<5.15.*
  • =<5.10.*
  • <d2afc7ecee476f9251dd87444f7fb6a424410922
  • <5.15.212
  • <6.12.96
  • <6.17
  • <34684a04777358b2b40ac729e54c8e45359e46b3
  • <6.17
  • ==fc7f732984ec91f30be3e574e0644066d07f2b78
  • <16ca053c2be5f4f3044dccf7fc19237dc820d394
  • <6.6.145
  • ==e7d2dc2421e821e4045775e6dc226378328de6f6
  • <f3461b84a4865d9b5e70fbb71da72ae044a3bcd2
  • =<6.6.*
  • <5.5
  • ==eec522fd0d28106b14a59ab2d658605febe4a3bb
  • <8f72fd25a57a457866350359ddd27a43caa62c95
  • <6.1.178
  • =<6.18.*
  • =<6.12.*
  • <d67aadee19ffdf3cc8520c5a4f4d5b2916d30baf
  • =<*