eeprom: ee1004: limit i2c reads to I2C_SMBUS_BLOCK_MAX
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
74650c34f93044d3ab441235f161f9e1e761e96b| No fix yet |
| Linux Linux |
| No fix yet |
In the Linux kernel, the following vulnerability has been resolved:
eeprom: ee1004: limit i2c reads to I2C_SMBUS_BLOCK_MAX
Commit effa453168a7 ("i2c: i801: Don't silently correct invalid transfer size") revealed that ee1004_eeprom_read() did not properly limit how many bytes to read at once.
In particular, i2c_smbus_read_i2c_block_data_or_emulated() takes the length to read as an u8. If count == 256 after taking into account the offset and page boundary, the cast to u8 overflows. And this is common when user space tries to read the entire EEPROM at once.
To fix it, limit each read to I2C_SMBUS_BLOCK_MAX (32) bytes, already the maximum length i2c_smbus_read_i2c_block_data_or_emulated() allows.
From the CVE record · Linux
The Linux kernel's ee1004 EEPROM read path can pass a 256-byte count to an I2C read function that accepts an 8-bit length, causing the count to overflow. This can occur when local user space reads an entire EEPROM at once; the input does not describe an authentication requirement or further impact.
Engineers running Linux kernels with the ee1004 EEPROM driver should check their vendor advisory for affected versions.