<?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 03:38:23 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-97480 — tty: serial: 8250: protect against NULL uart-&gt;port.dev in register</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-97480</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;tty: serial: 8250: protect against NULL uart-&amp;gt;port.dev in register&lt;/p&gt;
&lt;p&gt;serial8250_register_8250_port() conditionally copies uart-&amp;gt;port.dev
from up-&amp;gt;port.dev only when up-&amp;gt;port.dev is non-NULL:&lt;/p&gt;
&lt;p&gt;if (up-&amp;gt;port.dev) {
		uart-&amp;gt;port.dev = up-&amp;gt;port.dev;
		...
	}&lt;/p&gt;
&lt;p&gt;So if both the existing uart slot and up have a NULL -&amp;gt;dev,
uart-&amp;gt;port.dev remains NULL. The very next ACPI companion check
then dereferences it unconditionally:&lt;/p&gt;
&lt;p&gt;if (!has_acpi_companion(uart-&amp;gt;port.dev)) {&lt;/p&gt;
&lt;p&gt;has_acpi_companion() reads dev-&amp;gt;fwnode without a NULL guard
(include/linux/acpi.h), so this NULL-derefs the kernel for the
remaining no-dev case rather than just skipping the
mctrl_gpio_init() initialisation as intended.&lt;/p&gt;
&lt;p&gt;smatch flags the inconsistency:&lt;/p&gt;
&lt;p&gt;drivers/tty/serial/8250/8250_core.c:767
  serial8250_register_8250_port() error: &amp;#39;uart-&amp;gt;port.dev&amp;#39; could be
  null (see line 719)&lt;/p&gt;
&lt;p&gt;Guard the call with a NULL check so register continues to work
for callers that legitimately have no parent device (legacy
non-OF/non-ACPI registrations).&lt;/p&gt;
&lt;p&gt;No functional change for callers that pass a non-NULL -&amp;gt;dev.&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;tty: serial: 8250: protect against NULL uart-&amp;gt;port.dev in register&lt;/p&gt;
&lt;p&gt;serial8250_register_8250_port() conditionally copies uart-&amp;gt;port.dev
from up-&amp;gt;port.dev only when up-&amp;gt;port.dev is non-NULL:&lt;/p&gt;
&lt;p&gt;if (up-&amp;gt;port.dev) {
		uart-&amp;gt;port.dev = up-&amp;gt;port.dev;
		...
	}&lt;/p&gt;
&lt;p&gt;So if both the existing uart slot and up have a NULL -&amp;gt;dev,
uart-&amp;gt;port.dev remains NULL. The very next ACPI companion check
then dereferences it unconditionally:&lt;/p&gt;
&lt;p&gt;if (!has_acpi_companion(uart-&amp;gt;port.dev)) {&lt;/p&gt;
&lt;p&gt;has_acpi_companion() reads dev-&amp;gt;fwnode without a NULL guard
(include/linux/acpi.h), so this NULL-derefs the kernel for the
remaining no-dev case rather than just skipping the
mctrl_gpio_init() initialisation as intended.&lt;/p&gt;
&lt;p&gt;smatch flags the inconsistency:&lt;/p&gt;
&lt;p&gt;drivers/tty/serial/8250/8250_core.c:767
  serial8250_register_8250_port() error: &amp;#39;uart-&amp;gt;port.dev&amp;#39; could be
  null (see line 719)&lt;/p&gt;
&lt;p&gt;Guard the call with a NULL check so register continues to work
for callers that legitimately have no parent device (legacy
non-OF/non-ACPI registrations).&lt;/p&gt;
&lt;p&gt;No functional change for callers that pass a non-NULL -&amp;gt;dev.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-97480</guid>
    </item>
  </channel>
</rss>
