<?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>Mon, 28 Sep 2026 07:52:50 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-40296 — platform/x86: int3472: Fix double free of GPIO device during unregister</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-40296</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: int3472: Fix double free of GPIO device during unregister&lt;/p&gt;
&lt;p&gt;regulator_unregister() already frees the associated GPIO device. On
ThinkPad X9 (Lunar Lake), this causes a double free issue that leads to
random failures when other drivers (typically Intel THC) attempt to
allocate interrupts. The root cause is that the reference count of the
pinctrl_intel_platform module unexpectedly drops to zero when this
driver defers its probe.&lt;/p&gt;
&lt;p&gt;This behavior can also be reproduced by unloading the module directly.&lt;/p&gt;
&lt;p&gt;Fix the issue by removing the redundant release of the GPIO device
during regulator unregistration.&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: int3472: Fix double free of GPIO device during unregister&lt;/p&gt;
&lt;p&gt;regulator_unregister() already frees the associated GPIO device. On
ThinkPad X9 (Lunar Lake), this causes a double free issue that leads to
random failures when other drivers (typically Intel THC) attempt to
allocate interrupts. The root cause is that the reference count of the
pinctrl_intel_platform module unexpectedly drops to zero when this
driver defers its probe.&lt;/p&gt;
&lt;p&gt;This behavior can also be reproduced by unloading the module directly.&lt;/p&gt;
&lt;p&gt;Fix the issue by removing the redundant release of the GPIO device
during regulator unregistration.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-40296</guid>
    </item>
  </channel>
</rss>
