<?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-09-29T06:25:47.347465+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-64595</id>
    <title>CVE-2026-64595 — HID: hid-lenovo-go: cancel cfg_setup work in hid_go_cfg_remove()</title>
    <updated>2026-09-29T06:25:47.364504+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: hid-lenovo-go: cancel cfg_setup work in hid_go_cfg_remove()</p>
<p>hid_go_cfg_probe() initialises drvdata.go_cfg_setup and schedules it
to run 2 ms later:</p>
<p>INIT_DELAYED_WORK(&amp;drvdata.go_cfg_setup, &amp;cfg_setup);
    schedule_delayed_work(&amp;drvdata.go_cfg_setup, msecs_to_jiffies(2));</p>
<p>cfg_setup() dereferences drvdata.hdev to issue MCU command requests.
hid_go_cfg_remove() tears down sysfs and stops the HID device, but
never drains the delayed work.  If the device is unbound within the
2 ms scheduling delay (a probe failure rolling back via remove, or a
fast rmmod after probe), the work fires after hid_destroy_device()
has dropped its reference and released the underlying hdev struct,
leaving cfg_setup() with a stale drvdata.hdev pointer.</p>
<p>Mirror the sibling driver hid-lenovo-go-s.c, whose hid_gos_cfg_remove()
already calls cancel_delayed_work_sync() on its analogous work, and
drain go_cfg_setup at the top of hid_go_cfg_remove().  The cancel
must come before guard(mutex)(&amp;drvdata.cfg_mutex) because cfg_setup()
acquires that mutex; reversing the order would deadlock.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-64595"/>
  </entry>
</feed>
