tty: serial: 8250: protect against NULL uart->port.dev in register
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
tty: serial: 8250: protect against NULL uart->port.dev in register
serial8250_register_8250_port() conditionally copies uart->port.dev from up->port.dev only when up->port.dev is non-NULL:
if (up->port.dev) { uart->port.dev = up->port.dev; ... }
So if both the existing uart slot and up have a NULL ->dev, uart->port.dev remains NULL. The very next ACPI companion check then dereferences it unconditionally:
if (!has_acpi_companion(uart->port.dev)) {
has_acpi_companion() reads dev->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.
smatch flags the inconsistency:
From the CVE record · Linux
The Linux kernel’s 8250 serial port registration can dereference a NULL device pointer when a port has no parent device. This can crash the kernel; the input does not establish whether an attacker can trigger it or whether access or user interaction is required.
Engineers running Linux kernels that use the 8250 serial driver should check their kernel versions against the vendor advisory; affected versions were not provided.