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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HWeakness enumeration
Affected software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 872c8014e05ed47b8a7c0f5ba4311279a637150b, < a58400f58f82f3d8de9c067aa7cda690228c1ecc; >= 872c8014e05ed47b8a7c0f5ba4311279a637150b, < 58dfb6fe9dc80270cf7cc014837af4cbf928e3aa; >= 872c8014e05ed47b8a7c0f5ba4311279a637150b, < 387c86b582e0782ab332e7bfcd4e6e3f93922961 |
| Linux | Linux | 6.16 |
References
Timeline
- Published
- Jul 19, 2026
- Last modified
- Oct 30, 2026
- NVD status
- Analyzed