[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025091858-CVE-2023-53392-9703@gregkh>
Date: Thu, 18 Sep 2025 15:34:37 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-53392: HID: intel-ish-hid: Fix kernel panic during warm reset
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
HID: intel-ish-hid: Fix kernel panic during warm reset
During warm reset device->fw_client is set to NULL. If a bus driver is
registered after this NULL setting and before new firmware clients are
enumerated by ISHTP, kernel panic will result in the function
ishtp_cl_bus_match(). This is because of reference to
device->fw_client->props.protocol_name.
ISH firmware after getting successfully loaded, sends a warm reset
notification to remove all clients from the bus and sets
device->fw_client to NULL. Until kernel v5.15, all enabled ISHTP kernel
module drivers were loaded right after any of the first ISHTP device was
registered, regardless of whether it was a matched or an unmatched
device. This resulted in all drivers getting registered much before the
warm reset notification from ISH.
Starting kernel v5.16, this issue got exposed after the change was
introduced to load only bus drivers for the respective matching devices.
In this scenario, cros_ec_ishtp device and cros_ec_ishtp driver are
registered after the warm reset device fw_client NULL setting.
cros_ec_ishtp driver_register() triggers the callback to
ishtp_cl_bus_match() to match ISHTP driver to the device and causes kernel
panic in guid_equal() when dereferencing fw_client NULL pointer to get
protocol_name.
The Linux kernel CVE team has assigned CVE-2023-53392 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.16 with commit 44e2a58cb8803e3e40eaf5708c4d15b4118913c4 and fixed in 6.1.25 with commit 6c8cc40c588f8080a164d88336b1490279e0f1da
Issue introduced in 5.16 with commit 44e2a58cb8803e3e40eaf5708c4d15b4118913c4 and fixed in 6.2.12 with commit 45b9055a3a3ff6e8c08faad82ea36a8644a81587
Issue introduced in 5.16 with commit 44e2a58cb8803e3e40eaf5708c4d15b4118913c4 and fixed in 6.3 with commit 38518593ec55e897abda4b4be77b2ec8ec4447d1
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-2023-53392
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/intel-ish-hid/ishtp/bus.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/6c8cc40c588f8080a164d88336b1490279e0f1da
https://git.kernel.org/stable/c/45b9055a3a3ff6e8c08faad82ea36a8644a81587
https://git.kernel.org/stable/c/38518593ec55e897abda4b4be77b2ec8ec4447d1
Powered by blists - more mailing lists