In the Linux kernel, the following vulnerability has been resolved: HID: logitech-hidpp: fix race condition when accessing stale stack…
CVE-2026-99313
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.
Assessment
- CVSS
- Not yet scored
- Severity
- Unscored
- Known exploited
- Not listed in CISA KEV
- Exploit availability
- Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
- Published
- 18 November 2026
- Last updated
- 18 November 2026
- Assigner
- Linux
At the source
References
- https://git.kernel.org/stable/c/0fe696148d2c6486e52220aab822135ed7d05f38
- https://git.kernel.org/stable/c/88effb7680aea4fc9afaf5780a706f5f30d3de42
- https://git.kernel.org/stable/c/f427383e734e95af923ac470782ad9a3d1f0c276
- https://git.kernel.org/stable/c/8f282d12550e3beaf3fea782b5befa65f78b3c78
- https://git.kernel.org/stable/c/e320e65900f0e3bf2874e6f5091fec29384f4a60
- https://git.kernel.org/stable/c/4ed6f5d94cc86af5e1d4a2f5cdaf565d4d58300d
- https://git.kernel.org/stable/c/e2aaf2d3ad92ac4a8afa6b69ad4c38e7747d3d6e
Community proofs of concept
No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.
Submit a proof of concept
Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.
Query this programmatically
Agents can read this through the MCP endpoint, or over HTTP:
curl https://cve.zerocrew.in/api/cve/CVE-2026-99313