CVE-2026-99313 json
HID: logitech-hidpp: fix race condition when accessing stale stack pointer
published 2h ago modified 2h ago also EUVD-2026-128496
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, 6.18.54, 7.1
- git.kernel.org/stable/c/0fe696148d2c6486e52220aab822135ed7d05f38 commit
- git.kernel.org/stable/c/88effb7680aea4fc9afaf5780a706f5f30d3de42 commit
- git.kernel.org/stable/c/f427383e734e95af923ac470782ad9a3d1f0c276 commit
- git.kernel.org/stable/c/8f282d12550e3beaf3fea782b5befa65f78b3c78 commit
- git.kernel.org/stable/c/e320e65900f0e3bf2874e6f5091fec29384f4a60 commit
- git.kernel.org/stable/c/4ed6f5d94cc86af5e1d4a2f5cdaf565d4d58300d commit
- git.kernel.org/stable/c/e2aaf2d3ad92ac4a8afa6b69ad4c38e7747d3d6e commit
Is CVE-2026-99313 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/0fe696148d2c6486e52220aab822135ed7d05f38
- git.kernel.org /stable/c/88effb7680aea4fc9afaf5780a706f5f30d3de42
- git.kernel.org /stable/c/f427383e734e95af923ac470782ad9a3d1f0c276
- git.kernel.org /stable/c/8f282d12550e3beaf3fea782b5befa65f78b3c78
- git.kernel.org /stable/c/e320e65900f0e3bf2874e6f5091fec29384f4a60
- git.kernel.org /stable/c/4ed6f5d94cc86af5e1d4a2f5cdaf565d4d58300d
- git.kernel.org /stable/c/e2aaf2d3ad92ac4a8afa6b69ad4c38e7747d3d6e
Sources
- CVE List CVE-2026-99313
- NVD CVE-2026-99313
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.