DEBIAN-CVE-2023-53392
- Source
- https://security-tracker.debian.org/tracker/CVE-2023-53392
- Import Source
- https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2023-53392.json
- JSON Data
- https://api.osv.dev/v1/vulns/DEBIAN-CVE-2023-53392
- Upstream
- Published
- 2025-09-18T14:15:42Z
- Modified
- 2025-09-25T03:46:56.992413Z
- Summary
- [none]
- Details
-
In the Linux kernel, the following vulnerability has been resolved: HID: intel-ish-hid: Fix kernel panic during warm reset During warm reset device->fwclient 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 ishtpclbusmatch(). This is because of reference to device->fwclient->props.protocolname. ISH firmware after getting successfully loaded, sends a warm reset notification to remove all clients from the bus and sets device->fwclient 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, crosecishtp device and crosecishtp driver are registered after the warm reset device fwclient NULL setting. crosecishtp driverregister() triggers the callback to ishtpclbusmatch() to match ISHTP driver to the device and causes kernel panic in guidequal() when dereferencing fwclient NULL pointer to get protocol_name.
- References
Affected packages
Debian:12 / linux
Package
- Name
- linux
- Purl
- pkg:deb/debian/linux?arch=source
Debian:13 / linux
Package
- Name
- linux
- Purl
- pkg:deb/debian/linux?arch=source
Debian:14 / linux
Package
- Name
- linux
- Purl
- pkg:deb/debian/linux?arch=source