From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-99474: HID: hiddev: keep state alive through disconnect unlock
Date: Thu, 19 Nov 2026 15:26:12 +0100 [thread overview]
Message-ID: <2026111911-CVE-2026-99474-e16f@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
HID: hiddev: keep state alive through disconnect unlock
mutex_unlock() clears the mutex owner before taking its wait lock. A
thread spinning in the final hiddev file release can acquire
existancelock after hiddev_disconnect() clears the owner, then free
hiddev before the disconnecting thread reaches the mutex wait lock. This
causes a use-after-free in the mutex slow unlock path.
Give the connection and each open file an explicit reference. Drop each
reference only after its existancelock critical section has completed,
so neither unlock path can free the mutex while the other is still using
it.
The Linux kernel CVE team has assigned CVE-2026-99474 to this issue.
Affected and fixed versions
===========================
Issue introduced in 2.6.29 with commit 079034073faf974973baa0256b029451f6e768ad and fixed in 6.12.117 with commit 81e3e5ae4228f95414665877f5e487917fbef9c0
Issue introduced in 2.6.29 with commit 079034073faf974973baa0256b029451f6e768ad and fixed in 6.18.61 with commit 1b7b31f0d4bbfb9a87dd8acce1e001a3cf1c1623
Issue introduced in 2.6.29 with commit 079034073faf974973baa0256b029451f6e768ad and fixed in 7.3.2 with commit f214e9fe86a0aba6deb4a0b31b9998fb2b6879b5
Issue introduced in 2.6.29 with commit 079034073faf974973baa0256b029451f6e768ad and fixed in 7.4-rc1 with commit 03f449b5de36a25fc5eba7dabf2b4494389bdb91
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-99474
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/usbhid/hiddev.c
include/linux/hiddev.h
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/81e3e5ae4228f95414665877f5e487917fbef9c0
https://git.kernel.org/stable/c/1b7b31f0d4bbfb9a87dd8acce1e001a3cf1c1623
https://git.kernel.org/stable/c/f214e9fe86a0aba6deb4a0b31b9998fb2b6879b5
https://git.kernel.org/stable/c/03f449b5de36a25fc5eba7dabf2b4494389bdb91
reply other threads:[~2026-11-19 14:54 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=2026111911-CVE-2026-99474-e16f@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.