From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-68359: hwmon: (nzxt-smart2) Stop device IO before calling hid_hw_stop
Date: Mon, 10 Aug 2026 14:01:16 +0200 [thread overview]
Message-ID: <2026081040-CVE-2026-68359-dfca@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
hwmon: (nzxt-smart2) Stop device IO before calling hid_hw_stop
Calling hid_hw_stop() does not stop the device IO.
This results in a race condition between hid_input_report() and the point
immediately following the execution of hid_device_io_start() within
the driver probe function. If the probe operation fails after "io start"
has been initiated, this race condition will result in a UAF vulnerability.
Fix the problem by calling hid_device_io_stop() before calling
hid_hw_stop().
The Linux kernel CVE team has assigned CVE-2026-68359 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.17 with commit 53e68c20aeb1e23419bed811aa3a309ceda200f9 and fixed in 6.6.148 with commit 185c0880397aee9def0af5a59ea65f22f37ad658
Issue introduced in 5.17 with commit 53e68c20aeb1e23419bed811aa3a309ceda200f9 and fixed in 6.12.101 with commit a2a15de020597efbff84b4281dd472e5860b7e3e
Issue introduced in 5.17 with commit 53e68c20aeb1e23419bed811aa3a309ceda200f9 and fixed in 6.18.42 with commit 205cff797a94757ec88ba299c8e2bf2e1e3f4bbf
Issue introduced in 5.17 with commit 53e68c20aeb1e23419bed811aa3a309ceda200f9 and fixed in 7.1.6 with commit 18d7c523891004226bccdba39dd681eca22ceb8a
Issue introduced in 5.17 with commit 53e68c20aeb1e23419bed811aa3a309ceda200f9 and fixed in 7.2-rc5 with commit 59d104b54b0b42e30fd2a68d24ee5c49dcc54d1e
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-68359
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/hwmon/nzxt-smart2.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/185c0880397aee9def0af5a59ea65f22f37ad658
https://git.kernel.org/stable/c/a2a15de020597efbff84b4281dd472e5860b7e3e
https://git.kernel.org/stable/c/205cff797a94757ec88ba299c8e2bf2e1e3f4bbf
https://git.kernel.org/stable/c/18d7c523891004226bccdba39dd681eca22ceb8a
https://git.kernel.org/stable/c/59d104b54b0b42e30fd2a68d24ee5c49dcc54d1e
reply other threads:[~2026-08-10 12:13 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=2026081040-CVE-2026-68359-dfca@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.