<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 04:43:15 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64595 — HID: hid-lenovo-go: cancel cfg_setup work in hid_go_cfg_remove()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64595</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;HID: hid-lenovo-go: cancel cfg_setup work in hid_go_cfg_remove()&lt;/p&gt;
&lt;p&gt;hid_go_cfg_probe() initialises drvdata.go_cfg_setup and schedules it
to run 2 ms later:&lt;/p&gt;
&lt;p&gt;INIT_DELAYED_WORK(&amp;amp;drvdata.go_cfg_setup, &amp;amp;cfg_setup);
    schedule_delayed_work(&amp;amp;drvdata.go_cfg_setup, msecs_to_jiffies(2));&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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;amp;drvdata.cfg_mutex) because cfg_setup()
acquires that mutex; reversing the order would deadlock.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;HID: hid-lenovo-go: cancel cfg_setup work in hid_go_cfg_remove()&lt;/p&gt;
&lt;p&gt;hid_go_cfg_probe() initialises drvdata.go_cfg_setup and schedules it
to run 2 ms later:&lt;/p&gt;
&lt;p&gt;INIT_DELAYED_WORK(&amp;amp;drvdata.go_cfg_setup, &amp;amp;cfg_setup);
    schedule_delayed_work(&amp;amp;drvdata.go_cfg_setup, msecs_to_jiffies(2));&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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;amp;drvdata.cfg_mutex) because cfg_setup()
acquires that mutex; reversing the order would deadlock.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64595</guid>
    </item>
  </channel>
</rss>
