Skip to main content
No exploitation reportedFix availableAwaiting NVD analysis

CVE-2026-99313

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

No exploitation reported by the sources we read.

  • Published2026-11-18
  • Fixed in6.18.54 · 6.12.112 · 6.6.158 · 6.1.189 · 5.15.222 · 5.10.271

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2026-11-1808:42CVE publishedCNA

Versions per branch

OSV
Linux kernel
BranchAffectedFixed in
6.x≥ 6.13.0, < 6.18.546.18.54
6.x≥ 6.7.0, < 6.12.1126.12.112
6.x≥ 6.2.0, < 6.6.1586.6.158
6.1≥ 5.16.0, < 6.1.1896.1.189
5.x≥ 5.11.0, < 5.15.2225.15.222
5.10< 5.10.2715.10.271

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA2 products

As Linux, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Linuxother versions: not affected

    https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

    Affected
    • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 0fe696148d2c6486e52220aab822135ed7d05f38fixed in 0fe696148d2c6486e52220aab822135ed7d05f38git
    • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 88effb7680aea4fc9afaf5780a706f5f30d3de42fixed in 88effb7680aea4fc9afaf5780a706f5f30d3de42git
    • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < f427383e734e95af923ac470782ad9a3d1f0c276fixed in f427383e734e95af923ac470782ad9a3d1f0c276git
    • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 8f282d12550e3beaf3fea782b5befa65f78b3c78fixed in 8f282d12550e3beaf3fea782b5befa65f78b3c78git
    • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < e320e65900f0e3bf2874e6f5091fec29384f4a60fixed in e320e65900f0e3bf2874e6f5091fec29384f4a60git
    • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 4ed6f5d94cc86af5e1d4a2f5cdaf565d4d58300dfixed in 4ed6f5d94cc86af5e1d4a2f5cdaf565d4d58300dgit
    • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < e2aaf2d3ad92ac4a8afa6b69ad4c38e7747d3d6efixed in e2aaf2d3ad92ac4a8afa6b69ad4c38e7747d3d6egit
    • < 5.10.271fixed in 5.10.271semver

    5 more version lines in the CVE record.

  • Linuxother versions: affected

    https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

    Not affected ≥ 5.10.271, ≤ 5.10.* · ≥ 5.15.222, ≤ 5.15.* · ≥ 6.1.189, ≤ 6.1.* · ≥ 6.6.158, ≤ 6.6.* · ≥ 6.12.112, ≤ 6.12.* · ≥ 6.18.54, ≤ 6.18.* · ≥ 7.1

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-11-18

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • linuxUbuntu:Pro:20.04:LTSall versions · no fixed version listedand 21 other packages
  • linuxUbuntu:Pro:18.04:LTSall versions · no fixed version listedand 12 other packages
  • linuxUbuntu:Pro:16.04:LTSall versions · no fixed version listedand 7 other packages
  • linuxUbuntu:Pro:14.04:LTSall versions · no fixed version listedand 3 other packages
  • linuxUbuntu:26.10all versions · no fixed version listedand 8 other packages
  • linuxUbuntu:26.04:LTSall versions · no fixed version listedand 14 other packages
  • linuxUbuntu:24.04:LTSall versions · no fixed version listedand 52 other packages
  • linuxUbuntu:22.04:LTSall versions · no fixed version listedand 59 other packages

22 more package ranges on OSV.dev

Full record on NVD

Fix

  1. Update Linux kernel to 6.18.54 · 6.12.112 · 6.6.158 · 6.1.189 · 5.15.222 · 5.10.271

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Published
2026-11-18
Last Modified
2026-11-19
NVD status
Received
GitHub Advisory
GHSA-pr85-mhwv-8mh8

Frequently asked questions

What is 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->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.

Is CVE-2026-99313 actively exploited?

Active exploitation of CVE-2026-99313 has not been confirmed.

What is the CVSS score for CVE-2026-99313?

CVE-2026-99313 has a CVSS v3 base score of 8.8 (HIGH severity), with vector string CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Running Linux kernel? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record