hwmon: (pmbus/adm1266) reject short block-read responses in the GPIO accessors
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel fd9196aad9e5a3845cea17de3405ebc700382142, Kernel 64fa9328948ddcc0f7f3c23ea1756c126d9dffac, Kernel a2d1c819348b36fccbbfcf37c5fa7a50a9b4528f and 12 more.
In the Linux kernel, the following vulnerability has been resolved: hwmon: (pmbus/adm1266) reject short block-read responses in the GPIO accessors adm1266_gpio_get() and adm1266_gpio_get_multiple() both compose the pin-status word as pins_status = read_buf[0] + (read_buf[1] << 8); right after i2c_smbus_read_block_data(), guarding only against an error return. A well-behaved device returns 2 bytes for GPIO_STATUS/PDIO_STATUS, but the helper happily reports a 0- or 1-byte response too. If the device returns 0 bytes, both read_buf slots are uninitialized stack memory; if it returns 1 byte, read_buf[1] is. The composed value then flows through set_bit() into the caller's *bits in adm1266_gpio_get_multiple(), or into the return value of adm1266_gpio_get(), and ends up in userspace via gpiolib (sysfs and the char-dev ioctls). That leaks a few bits of kernel stack per request on any device whose firmware glitch, bus error, or hostile slave produces a short block-read response. Add the missing length check to both call sites and surface a short response as -EIO.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=d98dfad35c38c037b37c4adc99df01da571031a5 <fd9196aad9e5a3845cea17de3405ebc700382142, >=d98dfad35c38c037b37c4adc99df01da571031a5 <64fa9328948ddcc0f7f3c23ea1756c126d9dffac, >=d98dfad35c38c037b37c4adc99df01da571031a5 <a2d1c819348b36fccbbfcf37c5fa7a50a9b4528f, >=d98dfad35c38c037b37c4adc99df01da571031a5 <a7232f68c43ca62f545049b7f5fbfc75137b843b, >=d98dfad35c38c037b37c4adc99df01da571031a5 <ae25cf2ea9ebd06d7ad416647dbdc7b5d0172946, >=d98dfad35c38c037b37c4adc99df01da571031a5 <c603b6c6840ac0c6285f5eefea0de6242710af21, >=d98dfad35c38c037b37c4adc99df01da571031a5 <eb3cd9bb590460c6127145cb245be925d23f5232, >=d98dfad35c38c037b37c4adc99df01da571031a5 <ee4799becf7d2af3778007e22c2e55c4009a49c7, =5.10 | fd9196aad9e5a3845cea17de3405ebc700382142, 64fa9328948ddcc0f7f3c23ea1756c126d9dffac, a2d1c819348b36fccbbfcf37c5fa7a50a9b4528f, a7232f68c43ca62f545049b7f5fbfc75137b843b, ae25cf2ea9ebd06d7ad416647dbdc7b5d0172946, c603b6c6840ac0c6285f5eefea0de6242710af21, eb3cd9bb590460c6127145cb245be925d23f5232, ee4799becf7d2af3778007e22c2e55c4009a49c7 |
| linux-kernel: Kernel | >=5.11.0 <5.15.209, >=5.16.0 <6.1.175, >=6.13.0 <6.18.34, >=6.19.0 <7.0.11, >=6.2.0 <6.6.142, >=6.7.0 <6.12.92, >=5.10.0 <5.10.258 | 5.15.209, 6.1.175, 6.18.34, 7.0.11, 6.6.142, 6.12.92, 5.10.258 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket