Linux kernel stale stack pointer access in Logitech HID++ commands
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · < 4ed6f5d94cc86af5e1d4a2f5cdaf565d4d58300d| No fix yet |
| Linux Linux | — |
|
In the Linux kernel, the following vulnerability has been resolved:
HID: logitech-hidpp: fix race condition when accessing stale stack pointer
The driver uses hidpp->send_receive_buf to point to a stack-allocated buffer in the synchronous command path (__do_hidpp_send_message_sync). However, this pointer is not cleared when the function returns.
If an event is processed (e.g. by a different thread) while the send_mutex is held by a new command, but before that command has updated send_receive_buf, the handler (hidpp_raw_hidpp_event) will observe that the mutex is locked and dereference the stale pointer.
This results in an out-of-bounds access on a different thread's kernel stack (or a NULL pointer dereference on the very first command).
Fix this by: 1. Clearing hidpp->send_receive_buf to NULL before releasing the mutex in the synchronous command path. 2. Moving the assignment of the local 'question' and 'answer' pointers inside the mutex_is_locked() block in the handler, and adding a NULL check before dereferencing.
From the CVE record · Linux
The Linux kernel’s Logitech HID++ driver can retain a pointer to a stack buffer after a synchronous command returns. If an event is processed while a new command holds the mutex but before it updates that pointer, the event handler can access another thread’s kernel stack out of bounds; the first command can instead cause a NULL pointer dereference. The input does not establish whether an attacker can trigger this condition or what access it would require.
Engineers running Linux kernels with the Logitech HID++ driver should check their kernel; affected versions are not specified.