HID: i2c-hid: remove I2C_HID_READ_PENDING flag to prevent lock-up
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 4a200c3b9a40242652b5734630bdd0bcf3aca75f · < 29e94f295bad5be59cf4271a93e22cdcf5536722| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
HID: i2c-hid: remove I2C_HID_READ_PENDING flag to prevent lock-up
The flag I2C_HID_READ_PENDING is used to serialize I2C operations. However, this is not necessary, because I2C core already has its own locking for that.
More importantly, this flag can cause a lock-up: if the flag is set in i2c_hid_xfer() and an interrupt happens, the interrupt handler (i2c_hid_irq) will check this flag and return immediately without doing anything, then the interrupt handler will be invoked again in an infinite loop.
Since interrupt handler is an RT task, it takes over the CPU and the flag-clearing task never gets scheduled, thus we have a lock-up.
Delete this unnecessary flag.
From the CVE record · Linux
The Linux kernel’s i2c-hid driver can lock up when an interrupt occurs while the I2C_HID_READ_PENDING flag is set. The interrupt handler can then run repeatedly and prevent the task that clears the flag from being scheduled. The input does not establish an attacker path, authentication requirement, or user-interaction requirement.
Engineers running Linux kernels with the i2c-hid driver should check their kernel version; affected versions are not specified.