Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2023-53392

HID: intel-ish-hid: Fix kernel panic during warm reset

High7.1EPSS 0.15%
Published
Updated
Reserved
Assigned by
Linux

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.

Timeline

  1. ID reserved

    By Linux

  2. · 1 day later

    Published

  3. · 14 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2023-53392, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
EPSS (exploitation in 30 days)
0.15% · top 96% of all CVEs (7 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.1.

Affected products

  • Linux · Linux

    • affected 44e2a58cb8803e3e40eaf5708c4d15b4118913c4 – < 6c8cc40c588f8080a164d88336b1490279e0f1da
    • affected 44e2a58cb8803e3e40eaf5708c4d15b4118913c4 – < 45b9055a3a3ff6e8c08faad82ea36a8644a81587
    • affected 44e2a58cb8803e3e40eaf5708c4d15b4118913c4 – < 38518593ec55e897abda4b4be77b2ec8ec4447d1

  • Linux · Linux

    • affected 5.16
    • unaffected < 5.16
    • unaffected 6.1.25 – ≤ 6.1.*
    • unaffected 6.2.12 – ≤ 6.2.*
    • unaffected 6.3 – ≤ *

References (3)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-53392 badge
[![CVE-2023-53392](https://trackcve.app/badge/CVE-2023-53392.svg)](https://trackcve.app/cve/CVE-2023-53392)

Record last updated .