data built 2026-10-19T13:16:53Z

Look up another CVE · open CVE-2026-45877 in the interactive tracker

CVE-2026-45877

HID: intel-ish-hid: fix NULL-ptr-deref in ishtp_bus_remove_all_clients

EPSS 0.2%

Published 2026-05-27 (5 months ago) by the Linux kernel CNA. Subsystem drivers/hid. Debian urgency: not yet assigned.

What to do, per Debian release

Debian's own status for CVE-2026-45877 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source

ReleaseStatus VersionWhat this means
Debian 12bookwormvulnerable6.1.190-1No fix published anywhere yet, neither in Debian nor upstream for the series bookworm tracks. Watch the Debian tracker page for this CVE. Advisories for bookworm have historically landed a median of 23 days after publication.
Debian 13trixiefixed6.12.85-1Update the kernel and reboot. Fixed in 6.12.85-1. A running kernel keeps the old code until the machine restarts.
Debian 14forkyfixed6.18.14-1Update the kernel and reboot. Fixed in 6.18.14-1. A running kernel keeps the old code until the machine restarts.
Debian unstablesidfixed6.18.14-1Update the kernel and reboot. Fixed in 6.18.14-1. A running kernel keeps the old code until the machine restarts.

The vulnerability

What the bug is

During a warm reset flow, the cl->device pointer may be NULL if the reset occurs while clients are still being enumerated. Accessing cl->device->reference_count without a NULL check leads to a kernel panic. This issue was identified during multi-unit warm reboot stress clycles. Add a defensive NULL check for cl->device to ensure stability under such intensive testing conditions. KASAN: null-ptr-deref in range [0000000000000000-0000000000000007] Workqueue: ish_fw_update_wq fw_reset_work_fn Call Trace: ishtp_bus_remove_all_clients+0xbe/0x130 [intel_ishtp] ishtp_reset_handler+0x85/0x1a0 [intel_ishtp] fw_reset_work_fn+0x8a/0xc0 [intel_ish_ipc]

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

drivers/hid/intel-ish-hid/ishtp/bus.c

What this is
INTEL INTEGRATED SENSOR HUB DRIVERMAINTAINERS section matched on drivers/hid/intel-ish-hid/ · linux-input@vger.kernel.org · Maintained
Show whether Debian builds this, per release

Not established. This site could not find the build rule for the affected file in the kernel trees Debian ships, so it has no answer about whether Debian compiles this code. Read that as unknown, never as absent.

  • bookworm, trixie, forky, sid?
?
not established - no Makefile entry for the affected file

Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS

Signals

Published
2026-05-27 (5 months ago)source
CVSS
no vector published, unrated
Attack vector
not published
EPSS
0.16%, higher than 5.0% of all CVEssource
CISA KEV
not listedthe KEV catalogue
Debian urgency
not yet assignedsource
Subsystem
drivers/hid

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

IntroducedFixed inCommit
4.96.12.750b605e8ce606
4.96.18.14feb4bcfd4052
4.96.19.4272dac57caa9
4.97.056f7db581ee7

Why the CNA scored it this way

The kernel CNA published no CVSS vector and no reasoning for CVE-2026-45877, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.