<?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, 01 Oct 2026 20:46:57 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-31687 — gpio: omap: do not register driver in probe()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-31687</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: omap: do not register driver in probe()&lt;/p&gt;
&lt;p&gt;Commit 11a78b794496 (&amp;#34;ARM: OMAP: MPUIO wake updates&amp;#34;) registers the
omap_mpuio_driver from omap_mpuio_init(), which is called from
omap_gpio_probe().&lt;/p&gt;
&lt;p&gt;However, it neither makes sense to register drivers from probe()
callbacks of other drivers, nor does the driver core allow registering
drivers with a device lock already being held.&lt;/p&gt;
&lt;p&gt;The latter was revealed by commit dc23806a7c47 (&amp;#34;driver core: enforce
device_lock for driver_match_device()&amp;#34;) leading to a potential deadlock
condition described in [1].&lt;/p&gt;
&lt;p&gt;Additionally, the omap_mpuio_driver is never unregistered from the
driver core, even if the module is unloaded.&lt;/p&gt;
&lt;p&gt;Hence, register the omap_mpuio_driver from the module initcall and
unregister it in module_exit().&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: omap: do not register driver in probe()&lt;/p&gt;
&lt;p&gt;Commit 11a78b794496 (&amp;#34;ARM: OMAP: MPUIO wake updates&amp;#34;) registers the
omap_mpuio_driver from omap_mpuio_init(), which is called from
omap_gpio_probe().&lt;/p&gt;
&lt;p&gt;However, it neither makes sense to register drivers from probe()
callbacks of other drivers, nor does the driver core allow registering
drivers with a device lock already being held.&lt;/p&gt;
&lt;p&gt;The latter was revealed by commit dc23806a7c47 (&amp;#34;driver core: enforce
device_lock for driver_match_device()&amp;#34;) leading to a potential deadlock
condition described in [1].&lt;/p&gt;
&lt;p&gt;Additionally, the omap_mpuio_driver is never unregistered from the
driver core, even if the module is unloaded.&lt;/p&gt;
&lt;p&gt;Hence, register the omap_mpuio_driver from the module initcall and
unregister it in module_exit().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-31687</guid>
    </item>
  </channel>
</rss>
