<?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>Thu, 08 Oct 2026 11:24:46 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-44937 — platform/x86: intel-vbtn: Protect ACPI notify handler against recursion</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-44937</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-vbtn: 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-vbtn notify_handler() may
run on multiple CPU cores racing with themselves.&lt;/p&gt;
&lt;p&gt;This race gets hit on Dell Venue 7140 tablets when undocking from
the keyboard, causing the handler to try and register priv-&amp;gt;switches_dev
twice, as can be seen from the dev_info() message getting logged twice:&lt;/p&gt;
&lt;p&gt;[ 83.861800] intel-vbtn INT33D6:00: Registering Intel Virtual Switches input-dev after receiving a switch event
[ 83.861858] input: Intel Virtual Switches as /devices/pci0000:00/0000:00:1f.0/PNP0C09:00/INT33D6:00/input/input17
[ 83.861865] intel-vbtn INT33D6:00: Registering Intel Virtual Switches input-dev after receiving a switch event&lt;/p&gt;
&lt;p&gt;After which things go seriously wrong:
[ 83.861872] sysfs: cannot create duplicate filename &amp;#39;/devices/pci0000:00/0000:00:1f.0/PNP0C09:00/INT33D6:00/input/input17&amp;#39;
...
[ 83.861967] kobject: kobject_add_internal failed for input17 with -EEXIST, don&amp;#39;t try to register things with the same name in the same directory.
[ 83.877338] BUG: kernel NULL pointer dereference, address: 0000000000000018
...&lt;/p&gt;
&lt;p&gt;Protect intel-vbtn 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-vbtn: 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-vbtn notify_handler() may
run on multiple CPU cores racing with themselves.&lt;/p&gt;
&lt;p&gt;This race gets hit on Dell Venue 7140 tablets when undocking from
the keyboard, causing the handler to try and register priv-&amp;gt;switches_dev
twice, as can be seen from the dev_info() message getting logged twice:&lt;/p&gt;
&lt;p&gt;[ 83.861800] intel-vbtn INT33D6:00: Registering Intel Virtual Switches input-dev after receiving a switch event
[ 83.861858] input: Intel Virtual Switches as /devices/pci0000:00/0000:00:1f.0/PNP0C09:00/INT33D6:00/input/input17
[ 83.861865] intel-vbtn INT33D6:00: Registering Intel Virtual Switches input-dev after receiving a switch event&lt;/p&gt;
&lt;p&gt;After which things go seriously wrong:
[ 83.861872] sysfs: cannot create duplicate filename &amp;#39;/devices/pci0000:00/0000:00:1f.0/PNP0C09:00/INT33D6:00/input/input17&amp;#39;
...
[ 83.861967] kobject: kobject_add_internal failed for input17 with -EEXIST, don&amp;#39;t try to register things with the same name in the same directory.
[ 83.877338] BUG: kernel NULL pointer dereference, address: 0000000000000018
...&lt;/p&gt;
&lt;p&gt;Protect intel-vbtn 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-2024-44937</guid>
    </item>
  </channel>
</rss>
