HID: core: Harden s32ton() against conversion to 0 bits
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ dde5845a529ff753364a6d1aea61180946270bfa · < 8b4a94b1510f6a46ec48494b52ee8f67eb4fc836| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
HID: core: Harden s32ton() against conversion to 0 bits
Testing by the syzbot fuzzer showed that the HID core gets a shift-out-of-bounds exception when it tries to convert a 32-bit quantity to a 0-bit quantity. Ideally this should never occur, but there are buggy devices and some might have a report field with size set to zero; we shouldn't reject the report or the device just because of that.
Instead, harden the s32ton() routine so that it returns a reasonable result instead of crashing when it is called with the number of bits set to 0 -- the same as what snto32() does.
From the CVE record · Linux
The Linux kernel HID core can hit a shift-out-of-bounds exception when converting a 32-bit value to a zero-bit value. A HID device with a zero-sized report field can trigger the crash; the input does not establish remote access or authentication requirements.
Engineers running Linux kernels that process HID devices should check their exposure; affected versions are not specified.