<?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 15:10:05 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-90336 — serial: core: clear freed pointers on uart_register_driver() failure</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-90336</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;serial: core: clear freed pointers on uart_register_driver() failure&lt;/p&gt;
&lt;p&gt;uart_register_driver() leaves drv-&amp;gt;state pointing to freed memory when
tty_alloc_driver() fails. If tty_register_driver() fails, drv-&amp;gt;tty_driver
also retains a pointer after its reference is dropped.&lt;/p&gt;
&lt;p&gt;Drivers that use drv-&amp;gt;state as an &amp;#34;already registered&amp;#34; flag can then skip
registration on the next probe and pass the freed state to
uart_add_one_port().&lt;/p&gt;
&lt;p&gt;This issue was found with failslab on QEMU&amp;#39;s raspi1ap board by
failing registration and binding the PL011 port again.&lt;/p&gt;
&lt;p&gt;Clear both pointers on their failure paths, as uart_unregister_driver()
already does.&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;serial: core: clear freed pointers on uart_register_driver() failure&lt;/p&gt;
&lt;p&gt;uart_register_driver() leaves drv-&amp;gt;state pointing to freed memory when
tty_alloc_driver() fails. If tty_register_driver() fails, drv-&amp;gt;tty_driver
also retains a pointer after its reference is dropped.&lt;/p&gt;
&lt;p&gt;Drivers that use drv-&amp;gt;state as an &amp;#34;already registered&amp;#34; flag can then skip
registration on the next probe and pass the freed state to
uart_add_one_port().&lt;/p&gt;
&lt;p&gt;This issue was found with failslab on QEMU&amp;#39;s raspi1ap board by
failing registration and binding the PL011 port again.&lt;/p&gt;
&lt;p&gt;Clear both pointers on their failure paths, as uart_unregister_driver()
already does.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-90336</guid>
    </item>
  </channel>
</rss>
