CVE-2026-99313

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

Published Nov 18, 2026 CVSS n/a EPSS n/a KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

A race condition in the Linux logitech‑hidpp driver allows a concurrently running event handler to dereference a stale stack pointer that was set during a previous synchronous HID message. Because the send_receive_buf pointer is not cleared when the mutex is released, an incoming event that observes the locked mutex can proceed to dereference this stale pointer, leading to an out-of-bounds access on the kernel stack or a NULL pointer dereference. This flaw can cause a kernel crash or, if exploited, allow an attacker with local access to the Logitech HID device to corrupt kernel memory and potentially gain elevated privileges. The exact extent of impact is inferred from the nature of the out-of-bounds dereference, as the description does not explicitly state a privilege escalation outcome.

Affected Systems

All Linux kernel releases that include the logitech‑hidpp driver before the described commit. The vulnerability is present in the generic Linux kernel (CPE: cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*). No specific vendor distribution or version granularity is provided, so any kernel version using the default logitech‑hidpp implementation is potentially affected.

Risk and Exploitability

The CVSS score is not disclosed, and EPSS data is unavailable, indicating that exploitation may not have been observed yet. The flaw is local and requires physical access to a Logitech HID device that the system accepts. Because it results in kernel memory corruption, the risk is considered high if an attacker can trigger the race. The lack of a CISA KEV listing further suggests that, while serious, no public exploit is known at this time.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Linux kernel to a version that contains the commit which clears hidpp->send_receive_buf before the mutex is released.
  • Disable the logitech‑hidpp driver if the affected system does not need Logitech devices, e.g., by setting the kernel module blacklist or disabling the HID subsystem.
  • Physically disconnect or remove any Logitech HID device from the system to prevent local interaction that could trigger the race.

Generated by OpenCVE AI on November 18, 2026 at 23:14 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Weaknesses CWE-125
CWE-665
Type Values Removed Values Added
First Time appeared Linux linux
Vendors & Products Linux linux
Type Values Removed Values Added
Description 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.
Title HID: logitech-hidpp: fix race condition when accessing stale stack pointer
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Nov 18, 2026, 8:42 AM
Reserved
Sep 25, 2026, 10:25 AM
Status
Received
Published
Nov 18, 2026, 9:17 AM
Modified
Nov 18, 2026, 9:17 AM