i2c: qup: jump out of the loop in case of timeout
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ fbfab1ab065879370541caf0e514987368eb41b2 · < 42c4471b30fa203249f476dd42321cd7efb7f6a8| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
i2c: qup: jump out of the loop in case of timeout
Original logic only sets the return value but doesn't jump out of the loop if the bus is kept active by a client. This is not expected. A malicious or buggy i2c client can hang the kernel in this case and should be avoided. This is observed during a long time test with a PCA953x GPIO extender.
Fix it by changing the logic to not only sets the return value, but also jumps out of the loop and return to the caller with -ETIMEDOUT.
From the CVE record · Linux
The Linux kernel's i2c qup driver can remain in a loop after a timeout if an I2C client keeps the bus active. A malicious or buggy I2C client can cause the kernel to hang under that condition.
Teams running Linux kernels that use the i2c qup driver should check their versions; affected versions were not specified.