Skip to main content
Menu
CVEs

CVE

Linux kernel NULL pointer dereference in logitech-hidpp HID driver

CVE-2026-99313EUVD-2026-128496Published Updated Summary written by a model

Exploited
No known exploitation
Fix
Fixed in 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, and 2 more
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, or one of 2 more.

Summary

The Linux kernel's logitech-hidpp driver has a race condition in which a stale stack pointer can be dereferenced while a command is being sent. This can cause an out-of-bounds access on another thread's kernel stack or a NULL pointer dereference.

Original 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.

cve.now Index

20Pcve.now Index 20 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach20/20Affects Linux kernel (software on nearly every server, desktop or phone)
  • Severity?/10Unknown. No CVSS score or vendor rating
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 42 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, or one of 2 more.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-99313 (HID: logitech-hidpp: fix race condition when accessing stale stack pointer), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-99313 (entry last updated 2026-11-18):
Affected:
- Linux Linux: fixed in 5.10.271; fixed in 5.15.222; fixed in 6.1.189; fixed in 6.6.158; fixed in 6.12.112; fixed in 6.18.54
- Linux Linux: from 6.19, fixed in 7.1; from 6.13, fixed in 6.18.54; from 6.7, fixed in 6.12.112; from 6.2, fixed in 6.6.158; from 5.16, fixed in 6.1.189; from 5.11, fixed in 5.15.222; fixed in 5.10.271
Fixed versions: 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, 6.18.54, 7.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99313 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99313 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- 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
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-99313
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-99313"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • Linux Linux

    fixed in 5.10.271; fixed in 5.15.222; fixed in 6.1.189; fixed in 6.6.158; fixed in 6.12.112; fixed in 6.18.54

  • Linux Linux

    From 6.19 · fixed in 7.1; From 6.13 · fixed in 6.18.54; From 6.7 · fixed in 6.12.112; From 6.2 · fixed in 6.6.158; From 5.16 · fixed in 6.1.189; From 5.11 · fixed in 5.15.222; fixed in 5.10.271

Evidence 9

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-99313

Is CVE-2026-99313 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-99313?

Linux: before 5.10.271; before 5.15.222; before 6.1.189; before 6.6.158; before 6.12.112; before 6.18.54. Linux: from 6.19 before 7.1; from 6.13 before 6.18.54; from 6.7 before 6.12.112; from 6.2 before 6.6.158; from 5.16 before 6.1.189; from 5.11 before 5.15.222; before 5.10.271.Source: cve.now feed data

How do I fix CVE-2026-99313?

Upgrade to a fixed version: 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, or one of 2 more.Source: cve.now feed data

More CVEs