usb: idmouse: fix an uninit-value in idmouse_open
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 4244f72436ab77c3c29a6447af81734ab3925d85 · < 20b8c456df584ebb2387dc23d40ebe4ff334417c| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
usb: idmouse: fix an uninit-value in idmouse_open
In idmouse_create_image, if any ftip_command fails, it will go to the reset label. However, this leads to the data in bulk_in_buffer[HEADER..IMGSIZE] uninitialized. And the check for valid image incurs an uninitialized dereference.
Fix this by moving the check before reset label since this check only be valid if the data after bulk_in_buffer[HEADER] has concrete data.
Note that this is found by KMSAN, so only kernel compilation is tested.
From the CVE record · Linux
In the Linux kernel’s USB idmouse driver, a failed ftip_command in idmouse_create_image can leave part of bulk_in_buffer uninitialized before an image-validity check reads it. The input does not establish an attacker-controlled path or specify access, authentication, or user-interaction requirements; the finding was detected by KMSAN, and only kernel compilation was tested.
Engineers running Linux kernels with the USB idmouse driver should check their versions; affected versions were not specified.