<?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://db.gcve.eu</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 21:15:27 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-92482 — pinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip</title>
      <link>https://db.gcve.eu/vuln/cve-2026-92482</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;pinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip&lt;/p&gt;
&lt;p&gt;The gpio_chip is allocated with device-managed memory but registered with
the non-managed gpiochip_add_data(). This was harmless while the drivers
were built-in, but once they can be built as modules and unbound/rmmod&amp;#39;d,
devm frees the gpio_chip&amp;#39;s memory while it is still registered, causing a
use-after-free.&lt;/p&gt;
&lt;p&gt;Register it with devm_gpiochip_add_data() so it shares the same
device-managed lifecycle, which also lets the manual gpiochip_remove()
error paths go away.&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;pinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip&lt;/p&gt;
&lt;p&gt;The gpio_chip is allocated with device-managed memory but registered with
the non-managed gpiochip_add_data(). This was harmless while the drivers
were built-in, but once they can be built as modules and unbound/rmmod&amp;#39;d,
devm frees the gpio_chip&amp;#39;s memory while it is still registered, causing a
use-after-free.&lt;/p&gt;
&lt;p&gt;Register it with devm_gpiochip_add_data() so it shares the same
device-managed lifecycle, which also lets the manual gpiochip_remove()
error paths go away.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-92482</guid>
    </item>
  </channel>
</rss>
