CVE-2026-97480

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> tty: serial: 8250: protect against NULL uart-&gt;port.dev in register<br /> <br /> serial8250_register_8250_port() conditionally copies uart-&gt;port.dev<br /> from up-&gt;port.dev only when up-&gt;port.dev is non-NULL:<br /> <br /> if (up-&gt;port.dev) {<br /> uart-&gt;port.dev = up-&gt;port.dev;<br /> ...<br /> }<br /> <br /> So if both the existing uart slot and up have a NULL -&gt;dev,<br /> uart-&gt;port.dev remains NULL. The very next ACPI companion check<br /> then dereferences it unconditionally:<br /> <br /> if (!has_acpi_companion(uart-&gt;port.dev)) {<br /> <br /> has_acpi_companion() reads dev-&gt;fwnode without a NULL guard<br /> (include/linux/acpi.h), so this NULL-derefs the kernel for the<br /> remaining no-dev case rather than just skipping the<br /> mctrl_gpio_init() initialisation as intended.<br /> <br /> smatch flags the inconsistency:<br /> <br /> drivers/tty/serial/8250/8250_core.c:767<br /> serial8250_register_8250_port() error: &amp;#39;uart-&gt;port.dev&amp;#39; could be<br /> null (see line 719)<br /> <br /> Guard the call with a NULL check so register continues to work<br /> for callers that legitimately have no parent device (legacy<br /> non-OF/non-ACPI registrations).<br /> <br /> No functional change for callers that pass a non-NULL -&gt;dev.