From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-80770: HID: nintendo: stop device IO before hid_hw_stop on probe failure
Date: Fri, 4 Sep 2026 17:11:09 +0200 [thread overview]
Message-ID: <2026090401-CVE-2026-80770-d0ea@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
HID: nintendo: stop device IO before hid_hw_stop on probe failure
nintendo_hid_probe() calls hid_device_io_start() before joycon_init()
and joycon_leds_create(). If either fails, the error path jumps to
err_close which calls hid_hw_close()/hid_hw_stop() without first calling
hid_device_io_stop().
hid_hw_stop() does not stop device IO, so hid_input_report() may still
run and access driver data that is being torn down, resulting in a
use-after-free.
Add an err_io_stop label that calls hid_device_io_stop() before
hid_hw_close(), and point the two post-io_start error paths at it.
The Linux kernel CVE team has assigned CVE-2026-80770 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.16 with commit 2af16c1f846bd60240745bbd3afa13d5f040c61a and fixed in 6.1.187 with commit c2f3d51c7f5222f5b51e0c90f02258d82e1b44dd
Issue introduced in 5.16 with commit 2af16c1f846bd60240745bbd3afa13d5f040c61a and fixed in 6.6.156 with commit c023443f0e6cfd257846b6515c93c1ea08026593
Issue introduced in 5.16 with commit 2af16c1f846bd60240745bbd3afa13d5f040c61a and fixed in 6.12.106 with commit 03a84f9f88b42cd49752ec0259922b67e4b88598
Issue introduced in 5.16 with commit 2af16c1f846bd60240745bbd3afa13d5f040c61a and fixed in 6.18.47 with commit 5efcd7bbfaaec67d137c99aa0940fa34375db27f
Issue introduced in 5.16 with commit 2af16c1f846bd60240745bbd3afa13d5f040c61a and fixed in 7.1.11 with commit 13a3edf96568a0b7aacadea07c2adec53ac8f630
Issue introduced in 5.16 with commit 2af16c1f846bd60240745bbd3afa13d5f040c61a and fixed in 7.2.1 with commit 2e0d98dc8a6dea5fc2b72bf66e0dcbd5488644b4
Issue introduced in 5.16 with commit 2af16c1f846bd60240745bbd3afa13d5f040c61a and fixed in 7.3-rc1 with commit 1f74d3bff6fe04a64e02ab3661d2e0d554565aa6
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-80770
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-nintendo.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/c2f3d51c7f5222f5b51e0c90f02258d82e1b44dd
https://git.kernel.org/stable/c/c023443f0e6cfd257846b6515c93c1ea08026593
https://git.kernel.org/stable/c/03a84f9f88b42cd49752ec0259922b67e4b88598
https://git.kernel.org/stable/c/5efcd7bbfaaec67d137c99aa0940fa34375db27f
https://git.kernel.org/stable/c/13a3edf96568a0b7aacadea07c2adec53ac8f630
https://git.kernel.org/stable/c/2e0d98dc8a6dea5fc2b72bf66e0dcbd5488644b4
https://git.kernel.org/stable/c/1f74d3bff6fe04a64e02ab3661d2e0d554565aa6
reply other threads:[~2026-09-04 15:14 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=2026090401-CVE-2026-80770-d0ea@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.