<?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>Wed, 30 Sep 2026 02:05:03 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64603 — platform/x86: intel-hid: Protect ACPI notify handler against recursion</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64603</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;platform/x86: intel-hid: Protect ACPI notify handler against recursion&lt;/p&gt;
&lt;p&gt;Since commit e2ffcda16290 (&amp;#34;ACPI: OSL: Allow Notify () handlers to run on
all CPUs&amp;#34;) ACPI notify handlers like the intel-hid notify_handler() may
run on multiple CPU cores racing with themselves.&lt;/p&gt;
&lt;p&gt;On convertibles and detachables (matched by DMI chassis-type 31 and 32 in
dmi_auto_add_switch[]) the SW_TABLET_MODE input device is registered
lazily from notify_handler() on the first tablet-mode event, via
intel_hid_switches_setup(). When two such events race on different CPUs
both can pass the !priv-&amp;gt;switches check and register the priv-&amp;gt;switches
input device twice, resulting in a duplicate sysfs entry and a subsequent
NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;This is the same class of bug fixed by commit e075c3b13a0a (&amp;#34;platform/x86:
intel-vbtn: Protect ACPI notify handler against recursion&amp;#34;) for the
sibling intel-vbtn driver.&lt;/p&gt;
&lt;p&gt;Protect intel-hid notify_handler() from racing with itself with a mutex
to fix this.&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;platform/x86: intel-hid: Protect ACPI notify handler against recursion&lt;/p&gt;
&lt;p&gt;Since commit e2ffcda16290 (&amp;#34;ACPI: OSL: Allow Notify () handlers to run on
all CPUs&amp;#34;) ACPI notify handlers like the intel-hid notify_handler() may
run on multiple CPU cores racing with themselves.&lt;/p&gt;
&lt;p&gt;On convertibles and detachables (matched by DMI chassis-type 31 and 32 in
dmi_auto_add_switch[]) the SW_TABLET_MODE input device is registered
lazily from notify_handler() on the first tablet-mode event, via
intel_hid_switches_setup(). When two such events race on different CPUs
both can pass the !priv-&amp;gt;switches check and register the priv-&amp;gt;switches
input device twice, resulting in a duplicate sysfs entry and a subsequent
NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;This is the same class of bug fixed by commit e075c3b13a0a (&amp;#34;platform/x86:
intel-vbtn: Protect ACPI notify handler against recursion&amp;#34;) for the
sibling intel-vbtn driver.&lt;/p&gt;
&lt;p&gt;Protect intel-hid notify_handler() from racing with itself with a mutex
to fix this.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64603</guid>
    </item>
  </channel>
</rss>
