<?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 17:55:49 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-31732 — gpio: Fix resource leaks on errors in gpiochip_add_data_with_key()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-31732</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;gpio: Fix resource leaks on errors in gpiochip_add_data_with_key()&lt;/p&gt;
&lt;p&gt;Since commit aab5c6f20023 (&amp;#34;gpio: set device type for GPIO chips&amp;#34;),
`gdev-&amp;gt;dev.release` is unset.  As a result, the reference count to
`gdev-&amp;gt;dev` isn&amp;#39;t dropped on the error handling paths.&lt;/p&gt;
&lt;p&gt;Drop the reference on errors.&lt;/p&gt;
&lt;p&gt;Also reorder the instructions to make the error handling simpler.
Now gpiochip_add_data_with_key() roughly looks like:&lt;/p&gt;
&lt;p&gt;&amp;gt;&amp;gt;&amp;gt; Some memory allocation.  Go to ERR ZONE 1 on errors.
   &amp;gt;&amp;gt;&amp;gt; device_initialize().&lt;/p&gt;
&lt;p&gt;gpiodev_release() takes over the responsibility for freeing the
   resources of `gdev-&amp;gt;dev`.  The subsequent error handling paths
   shouldn&amp;#39;t go through ERR ZONE 1 again which leads to double free.&lt;/p&gt;
&lt;p&gt;&amp;gt;&amp;gt;&amp;gt; Some initialization mainly on `gdev`.
   &amp;gt;&amp;gt;&amp;gt; The rest of initialization.  Go to ERR ZONE 2 on errors.
   &amp;gt;&amp;gt;&amp;gt; Chip registration success and exit.&lt;/p&gt;
&lt;p&gt;&amp;gt;&amp;gt;&amp;gt; ERR ZONE 2.  gpio_device_put() and exit.
   &amp;gt;&amp;gt;&amp;gt; ERR ZONE 1.&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;gpio: Fix resource leaks on errors in gpiochip_add_data_with_key()&lt;/p&gt;
&lt;p&gt;Since commit aab5c6f20023 (&amp;#34;gpio: set device type for GPIO chips&amp;#34;),
`gdev-&amp;gt;dev.release` is unset.  As a result, the reference count to
`gdev-&amp;gt;dev` isn&amp;#39;t dropped on the error handling paths.&lt;/p&gt;
&lt;p&gt;Drop the reference on errors.&lt;/p&gt;
&lt;p&gt;Also reorder the instructions to make the error handling simpler.
Now gpiochip_add_data_with_key() roughly looks like:&lt;/p&gt;
&lt;p&gt;&amp;gt;&amp;gt;&amp;gt; Some memory allocation.  Go to ERR ZONE 1 on errors.
   &amp;gt;&amp;gt;&amp;gt; device_initialize().&lt;/p&gt;
&lt;p&gt;gpiodev_release() takes over the responsibility for freeing the
   resources of `gdev-&amp;gt;dev`.  The subsequent error handling paths
   shouldn&amp;#39;t go through ERR ZONE 1 again which leads to double free.&lt;/p&gt;
&lt;p&gt;&amp;gt;&amp;gt;&amp;gt; Some initialization mainly on `gdev`.
   &amp;gt;&amp;gt;&amp;gt; The rest of initialization.  Go to ERR ZONE 2 on errors.
   &amp;gt;&amp;gt;&amp;gt; Chip registration success and exit.&lt;/p&gt;
&lt;p&gt;&amp;gt;&amp;gt;&amp;gt; ERR ZONE 2.  gpio_device_put() and exit.
   &amp;gt;&amp;gt;&amp;gt; ERR ZONE 1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-31732</guid>
    </item>
  </channel>
</rss>
