serial: core: clear freed pointers on uart_register_driver() failure
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · < 61a2fb25551be0375bc16ef2a70c987dfca26183| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
serial: core: clear freed pointers on uart_register_driver() failure
uart_register_driver() leaves drv->state pointing to freed memory when tty_alloc_driver() fails. If tty_register_driver() fails, drv->tty_driver also retains a pointer after its reference is dropped.
Drivers that use drv->state as an "already registered" flag can then skip registration on the next probe and pass the freed state to uart_add_one_port().
This issue was found with failslab on QEMU's raspi1ap board by failing registration and binding the PL011 port again.
Clear both pointers on their failure paths, as uart_unregister_driver() already does.
From the CVE record · Linux
The Linux kernel serial core can retain pointers to freed memory if UART driver registration fails. On a later probe, a driver that uses the retained state as a registration flag may pass freed memory to uart_add_one_port(); the input does not describe a network attack, authentication requirement, or user interaction.
Engineers running Linux kernels with UART serial drivers should check their kernel version against the vendor advisory; affected versions are not specified.