CVE-2026-99313: Linux kernel · HID: logitech-hidpp: fix race condition when accessing stale stack pointer
Source GCVE Database
Not known to be exploited · fixed in f427383e734e95af923ac470782ad9a3d1f0c276 : patch Linux kernel soon.
Data as of 18 Nov 2026, 10:51 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in f427383e734e95af923ac470782ad9a3d1f0c276, e320e65900f0e3bf2874e6f5091fec29384f4a60, e2aaf2d3ad92ac4a8afa6b69ad4c38e7747d3d6e +10
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
Red Hatredhat/kernelpkg:rpm/redhat/kernelOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The vulnerability has been resolved by clearing the stale pointer before releasing the mutex and adjusting pointer usage within the locked section. Since a fix is described, users should apply the updated Linux kernel version containing this patch once available. Patch status is not explicitly confirmed in the input; check the vendor or kernel advisory for the official fixed version and update accordingly.
Description
A race condition vulnerability in the Linux kernel's logitech-hidpp driver allows a stale stack pointer to be accessed, leading to out-of-bounds memory access or a NULL pointer dereference. The flaw occurs because a pointer to a stack-allocated buffer is not cleared after use, causing unsafe dereferencing in concurrent threads.
References
- nvd.nist.gov/vuln/detail/CVE-2026-99313 (opens in a new tab)
- git.kernel.org/stable/c/0fe696148d2c6486e52220aab822135ed7d05f38 (opens in a new tab)
- git.kernel.org/stable/c/4ed6f5d94cc86af5e1d4a2f5cdaf565d4d58300d (opens in a new tab)
- git.kernel.org/stable/c/88effb7680aea4fc9afaf5780a706f5f30d3de42 (opens in a new tab)
- git.kernel.org/stable/c/8f282d12550e3beaf3fea782b5befa65f78b3c78 (opens in a new tab)
- git.kernel.org/stable/c/e2aaf2d3ad92ac4a8afa6b69ad4c38e7747d3d6e (opens in a new tab)
- git.kernel.org/stable/c/e320e65900f0e3bf2874e6f5091fec29384f4a60 (opens in a new tab)
- git.kernel.org/stable/c/f427383e734e95af923ac470782ad9a3d1f0c276 (opens in a new tab)