CVE-2026-99313

published 18 Nov 2026 · updated 20 Nov 2026

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

8.8HighCVSS 8.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 3.19, Kernel 0fe696148d2c6486e52220aab822135ed7d05f38, Kernel 4ed6f5d94cc86af5e1d4a2f5cdaf565d4d58300d and 11 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=3.18.17 <3.19, >=2f31c52529103d8f0e1485272064f982d14ce54a <0fe696148d2c6486e52220aab822135ed7d05f38, >=2f31c52529103d8f0e1485272064f982d14ce54a <4ed6f5d94cc86af5e1d4a2f5cdaf565d4d58300d, >=2f31c52529103d8f0e1485272064f982d14ce54a <88effb7680aea4fc9afaf5780a706f5f30d3de42, >=2f31c52529103d8f0e1485272064f982d14ce54a <8f282d12550e3beaf3fea782b5befa65f78b3c78, >=2f31c52529103d8f0e1485272064f982d14ce54a <e2aaf2d3ad92ac4a8afa6b69ad4c38e7747d3d6e, >=2f31c52529103d8f0e1485272064f982d14ce54a <e320e65900f0e3bf2874e6f5091fec29384f4a60, >=2f31c52529103d8f0e1485272064f982d14ce54a <f427383e734e95af923ac470782ad9a3d1f0c276, =3.19, =bd28e66ce1fb42696c351aad8f736570938a27123.19, 0fe696148d2c6486e52220aab822135ed7d05f38, 4ed6f5d94cc86af5e1d4a2f5cdaf565d4d58300d, 88effb7680aea4fc9afaf5780a706f5f30d3de42, 8f282d12550e3beaf3fea782b5befa65f78b3c78, e2aaf2d3ad92ac4a8afa6b69ad4c38e7747d3d6e, e320e65900f0e3bf2874e6f5091fec29384f4a60, f427383e734e95af923ac470782ad9a3d1f0c276
linux-kernel: Kernel>=3.19.0 <5.10.271, >=5.11.0 <5.15.222, >=5.16.0 <6.1.189, >=6.13.0 <6.18.54, >=6.2.0 <6.6.158, >=6.7.0 <6.12.112, >=3.18.17 <3.195.10.271, 5.15.222, 6.1.189, 6.18.54, 6.6.158, 6.12.112, 3.19

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-99313 severity on Zeptric[![CVE-2026-99313](https://zeptric.io/badge/cve/CVE-2026-99313.svg)](https://zeptric.io/cve/CVE-2026-99313)