All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-99313: HID: logitech-hidpp: fix race condition when accessing stale stack pointer
Date: Wed, 18 Nov 2026 09:42:14 +0100	[thread overview]
Message-ID: <2026111814-CVE-2026-99313-63fa@gregkh> (raw)

From: Greg Kroah-Hartman <gregkh@kernel.org>

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.

The Linux kernel CVE team has assigned CVE-2026-99313 to this issue.


Affected and fixed versions
===========================

	Fixed in 5.10.271 with commit 0fe696148d2c6486e52220aab822135ed7d05f38
	Fixed in 5.15.222 with commit 88effb7680aea4fc9afaf5780a706f5f30d3de42
	Fixed in 6.1.189 with commit f427383e734e95af923ac470782ad9a3d1f0c276
	Fixed in 6.6.158 with commit 8f282d12550e3beaf3fea782b5befa65f78b3c78
	Fixed in 6.12.112 with commit e320e65900f0e3bf2874e6f5091fec29384f4a60
	Fixed in 6.18.54 with commit 4ed6f5d94cc86af5e1d4a2f5cdaf565d4d58300d
	Fixed in 7.1 with commit e2aaf2d3ad92ac4a8afa6b69ad4c38e7747d3d6e

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2026-99313
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/hid/hid-logitech-hidpp.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	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

                 reply	other threads:[~2026-11-18  8:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2026111814-CVE-2026-99313-63fa@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=cve@kernel.org \
    --cc=gregkh@kernel.org \
    --cc=linux-cve-announce@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.