Skip to content
statance
MenuClose
high · CVSS 8.8

CVE-2026-99313

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

Published 18 Nov 2026 · Source updated 19 Nov 2026 · Retrieved 2026-11-19 14:23 UTC

Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

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.

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
LinuxLinuxaffected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to < 0fe696148d2c6486e52220aab822135ed7d05f38; affected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to < 88effb7680aea4fc9afaf5780a706f5f30d3de42; affected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to < f427383e734e95af923ac470782ad9a3d1f0c276; affected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to < 8f282d12550e3beaf3fea782b5befa65f78b3c78; affected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to < e320e65900f0e3bf2874e6f5091fec29384f4a60; affected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to < 4ed6f5d94cc86af5e1d4a2f5cdaf565d4d58300d; affected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to < e2aaf2d3ad92ac4a8afa6b69ad4c38e7747d3d6e; affected: 0 to < 5.10.271; affected: 0 to < 5.15.222; affected: 0 to < 6.1.189; affected: 0 to < 6.6.158; affected: 0 to < 6.12.112; affected: 0 to < 6.18.54See vendor advisory
LinuxLinuxunaffected: 5.10.271 to ≤ 5.10.*; unaffected: 5.15.222 to ≤ 5.15.*; unaffected: 6.1.189 to ≤ 6.1.*; unaffected: 6.6.158 to ≤ 6.6.*; unaffected: 6.12.112 to ≤ 6.12.*; unaffected: 6.18.54 to ≤ 6.18.*; unaffected: 7.1 to ≤ *See vendor advisory

Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.

Is it being exploited?

This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.

CISA data retrieved 2026-11-19 21:16 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed