CVE-2026-99313: HID: logitech-hidpp: fix race condition when accessing stale stack pointer

Published Nov 18, 2026
·
Updated

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->sendreceivebuf to point to a stack-allocated buffer in the synchronous command path (dohidppsendmessagesync). However, this pointer is not cleared when the function returns.

If an event is processed (e.g. by a different thread) while the sendmutex is held by a new command, but before that command has updated sendreceivebuf, the handler (hidpprawhidppevent) 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->sendreceivebuf to NULL before releasing the mutex in the synchronous command path. 2. Moving the assignment of the local 'question' and 'answer' pointers inside the mutexislocked() block in the handler, and adding a NULL check before dereferencing.

Affected Software

1 affected component
Linux Linux kernel

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Compensating control

    In the Linux kernel Logitech HID++ driver, move the local question and answer pointer assignments inside the mutex_is_locked() block, check for NULL before dereferencing, and clear hidpp->send_receive_buf to NULL before releasing the mutex.

Event History

Nov 18, 2026
CVE Published
via MITRE·08:42 AM
Data Sourced
via MITRE·08:42 AM
Description

Frequently Asked Questions

1

What systems are exposed to this issue?

Systems using the Linux kernel Logitech HID++ driver are exposed when the driver processes HID++ events alongside synchronous commands. The affected condition involves concurrent event handling and command processing in the driver.

2

What conditions are needed to trigger the flaw?

An HID++ event must be processed by another thread while the synchronous-command mutex is held for a new command, before the new command updates the shared receive-buffer pointer. On the first command, the stale pointer condition can instead result in a NULL pointer dereference.

3

What can happen if the race is triggered?

The event handler can dereference a stale pointer to another thread's kernel stack, causing an out-of-bounds access. It may also dereference NULL during the first command path.

4

What does the available fix change?

The fix clears the shared receive-buffer pointer before releasing the mutex in the synchronous command path. It also limits pointer assignment to the locked-handler path and checks for NULL before dereferencing the pointer.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203