CyberRota Analysis
AI-GeneratedThe vulnerability affects the Linux kernel's bmp580_trigger_handler function, which improperly handles stack memory by not initializing a scan buffer before copying sensor data. This oversight can lead to the leakage of uninitialized memory to user space, potentially exposing sensitive information. Organizations using affected Linux kernel versions, particularly those relying on the bmp580 sensor, should prioritize this fix to mitigate the risk of data exposure.
Original NVD Description
In the Linux kernel, the following vulnerability has been resolved: iio: pressure: bmp280: fix stack leak in bmp580 trigger handler bmp580_trigger_handler() declares its scan buffer on the stack without an initializer and then memcpy()s 3 bytes of 24-bit sensor data into each 4-byte __le32 field. The high byte of comp_temp and comp_press is left uninitialized, and the channel storagebits is 32, so two bytes of stack are pushed to userspace per scan. This is a regression from when the buffer lived in the private data, the move to a stack-local struct dropped the implicit zeroing. bme280_trigger_handler() was fixed up to handle this bug, but this driver was not fixed because there was no padding hole, but rather a short-fill issue. Fix this all by just zero-initializing the structure on the stack.