hwmon: (pmbus/q54sj108a2) fix stack overflow in debugfs read
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ d014538aa38561cd24c5eb228223585f26c5ec71 · < 24a7b9daa103fa963b3fd37d8805b23e01621976| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
hwmon: (pmbus/q54sj108a2) fix stack overflow in debugfs read
The q54sj108a2_debugfs_read function suffers from a stack buffer overflow due to incorrect arguments passed to bin2hex(). The function currently passes 'data' as the destination and 'data_char' as the source.
Because bin2hex() converts each input byte into two hex characters, a 32-byte block read results in 64 bytes of output. Since 'data' is only 34 bytes (I2C_SMBUS_BLOCK_MAX + 2), this writes 30 bytes past the end of the buffer onto the stack.
Additionally, the arguments were swapped: it was reading from the zero-initialized 'data_char' and writing to 'data', resulting in all-zero output regardless of the actual I2C read.
Fix this by: 1. Expanding 'data_char' to 66 bytes to safely hold the hex output. 2. Correcting the bin2hex() argument order and using the actual read count. 3. Using a pointer to select the correct output buffer for the final simple_read_from_buffer call.
From the CVE record · Linux
The Linux kernel’s q54sj108a2 hardware-monitoring driver has a stack buffer overflow in its debugfs read function. A local user who can read the affected debugfs entry can trigger an out-of-bounds stack write; the function also returns all-zero output instead of the I2C data.
Engineers running Linux kernels with the q54sj108a2 driver should check whether their kernel includes the fix; affected versions are not specified.