mctp i2c: initialise event handler read bytes
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ f5b8abf9fc3dacd7529d363e26fe8230935d65f8 · < 2a14e91b6d76639dac70ea170f4384c1ee3cb48d| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
mctp i2c: initialise event handler read bytes
Set a 0xff value for i2c reads of an mctp-i2c device. Otherwise reads will return "val" from the i2c bus driver. For i2c-aspeed and i2c-npcm7xx that is a stack uninitialised u8.
Tested with "i2ctransfer -y 1 r10@0x34" where 0x34 is a mctp-i2c instance, now it returns all 0xff.
From the CVE record · Linux
The Linux kernel’s mctp-i2c event handler does not initialise bytes returned by I2C reads. On i2c-aspeed and i2c-npcm7xx, a read of an mctp-i2c device can return an uninitialised stack byte. The input does not specify authentication requirements or whether user interaction is needed.
Engineers running Linux kernels with mctp-i2c and the i2c-aspeed or i2c-npcm7xx bus driver should check their systems; affected versions are not specified.