<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-03T07:49:04.028323+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-45877</id>
    <title>CVE-2026-45877 — HID: intel-ish-hid: fix NULL-ptr-deref in ishtp_bus_remove_all_clients</title>
    <updated>2026-10-03T07:49:04.032321+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>HID: intel-ish-hid: fix NULL-ptr-deref in ishtp_bus_remove_all_clients</p>
<p>During a warm reset flow, the cl-&gt;device pointer may be NULL if the
reset occurs while clients are still being enumerated. Accessing
cl-&gt;device-&gt;reference_count without a NULL check leads to a kernel panic.</p>
<p>This issue was identified during multi-unit warm reboot stress clycles.
Add a defensive NULL check for cl-&gt;device to ensure stability under
such intensive testing conditions.</p>
<p>KASAN: null-ptr-deref in range [0000000000000000-0000000000000007]
Workqueue: ish_fw_update_wq fw_reset_work_fn</p>
<p>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]</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-45877"/>
  </entry>
</feed>
