Input: iforce - invert valid length check when fetching device IDs
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Input: iforce - invert valid length check when fetching device IDs
syzbot is reporting uninitialized value at iforce_init_device() [1], for commit 6ac0aec6b0a6 ("Input: iforce - allow callers supply data buffer when fetching device IDs") is checking that valid length is shorter than bytes to read. Since iforce_get_id_packet() stores valid length when returning 0, the caller needs to check that valid length is longer than or equals to bytes to read.
From the CVE record · Linux
The Linux kernel's iforce input driver uses an inverted valid-length check when fetching device IDs. This can cause iforce_init_device() to use an uninitialized value. The input does not specify an attacker action or whether authentication, network access, or user interaction is required.
Engineers running Linux kernels with the iforce input driver should check their kernel versions; affected versions are not specified.