From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-80774: HID: asus: fix missing hid_is_usb() check
Date: Fri, 4 Sep 2026 17:11:13 +0200 [thread overview]
Message-ID: <2026090402-CVE-2026-80774-1ed5@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
HID: asus: fix missing hid_is_usb() check
to_usb_interface() can only be used on a hid_device whose parent is really
USB; uhid can create devices that identify as being on BUS_USB, but don't
actually have a USB parent.
Fix the use of to_usb_interface() without a hid_is_usb() check.
I have verified that it is currently possible to trigger a kernel splat due
to this bug in an ASAN build, and that this commit fixes the issue.
The Linux kernel CVE team has assigned CVE-2026-80774 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.12.35 with commit ff38cf0bd888fe15789a7193d07c4a876388d520 and fixed in 6.12.108 with commit bdb2e0a2a359e473ca5619e35adee89028697239
Issue introduced in 6.16 with commit 00e005c952f74f50a3f86af96f56877be4685e14 and fixed in 6.18.49 with commit 8b5debb6252cd1e2b6c7adf8f95761a0e743d2cf
Issue introduced in 6.16 with commit 00e005c952f74f50a3f86af96f56877be4685e14 and fixed in 7.1.11 with commit 1ddc2f5913bec7a846544d51a8f7a8119573b2a1
Issue introduced in 6.16 with commit 00e005c952f74f50a3f86af96f56877be4685e14 and fixed in 7.2.1 with commit ee883906cf6685d753af9c2d2ca9fd6f63197726
Issue introduced in 6.16 with commit 00e005c952f74f50a3f86af96f56877be4685e14 and fixed in 7.3-rc1 with commit 02bf61dfb44f17ec187d1da1a82495951bbd12df
Issue introduced in 6.15.4 with commit 02d5431198f10e7c6e31f4138c14cfe400ec55a7
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-80774
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-asus.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/bdb2e0a2a359e473ca5619e35adee89028697239
https://git.kernel.org/stable/c/8b5debb6252cd1e2b6c7adf8f95761a0e743d2cf
https://git.kernel.org/stable/c/1ddc2f5913bec7a846544d51a8f7a8119573b2a1
https://git.kernel.org/stable/c/ee883906cf6685d753af9c2d2ca9fd6f63197726
https://git.kernel.org/stable/c/02bf61dfb44f17ec187d1da1a82495951bbd12df
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=2026090402-CVE-2026-80774-1ed5@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.