Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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

  1. ID reserved

    By Linux

  2. · 54 days later

    Published

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
Not scored

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 0fe696148d2c6486e52220aab822135ed7d05f38
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 88effb7680aea4fc9afaf5780a706f5f30d3de42
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < f427383e734e95af923ac470782ad9a3d1f0c276
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 8f282d12550e3beaf3fea782b5befa65f78b3c78
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < e320e65900f0e3bf2874e6f5091fec29384f4a60
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 4ed6f5d94cc86af5e1d4a2f5cdaf565d4d58300d
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < e2aaf2d3ad92ac4a8afa6b69ad4c38e7747d3d6e
    • affected < 5.10.271
    • affected < 5.15.222
    • affected < 6.1.189
    • affected < 6.6.158
    • affected < 6.12.112
    • affected < 6.18.54
  • Linux · Linux

    • unaffected 5.10.271 – ≤ 5.10.*
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.54 – ≤ 6.18.*
    • unaffected 7.1 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-99313 badge
[![CVE-2026-99313](https://cveledger.app/badge/CVE-2026-99313.svg)](https://cveledger.app/cve/CVE-2026-99313)

Record last updated .