serial: 8250_dw: unregister 8250 port if clk_notifier_register() fails
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 57f83e5dd6a33c4696699954784f8fee789b1d0c · < 778b9dda4b24005a27bcd9c35c110bf8d7f259ca| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
serial: 8250_dw: unregister 8250 port if clk_notifier_register() fails
dw8250_probe() registers the 8250 port via serial8250_register_8250_port() and then, if the device has a clock, registers a clock notifier. If clk_notifier_register() fails, probe returns the error but leaves the 8250 port registered. The matching serial8250_unregister_port() lives in dw8250_remove(), which is not called when probe fails, so the port slot stays occupied until the device is rebound or the system is rebooted. The devm-allocated driver data is freed while the port still references it (via the saved private_data and serial_in/serial_out callbacks), so any access to that port slot before a rebind is a use-after-free hazard.
Unregister the port on the clk_notifier_register() error path.
From the CVE record · Linux
The Linux kernel’s 8250_dw driver can leave a serial port registered if clock notifier registration fails during device probe. Its driver data is then freed, and access to the port slot before a device rebind can cause a use-after-free. The input does not specify whether an attacker can trigger the failure or whether access requires authentication or user interaction.
Engineers running Linux kernels with the 8250_dw serial driver should check their kernel; affected versions were not provided.