9.8 CRITICAL
- CVSS version (CVSS): 3.1
- Attack Vector (AV): Network (N)
- Attack Complexity (AC): Low (L)
- Privileges Required (PR): None (N)
- User Interaction (UI): None (N)
- Scope (S): Unchanged (U)
- Confidentiality (C): High (H)
- Integrity (I): High (H)
- Availability (A): High (H)
- Modified Attack Vector (MAV): Network (N)
- Modified Attack Complexity (MAC): Low (L)
- Modified Privileges Required (MPR): None (N)
- Modified User Interaction (MUI): None (N)
- Modified Confidentiality (MC): High (H)
- Modified Scope (MS): Unchanged (U)
- Modified Integrity (MI): High (H)
- Modified Availability (MA): High (H)
Activity log
- Created & dismissed (max. allowed matches exceeded) suggestion
serial: 8250_dw: unregister 8250 port if clk_notifier_register() fails
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.
References
Affected products
- <d72650a4f334581b23a1892b888a4cb1be142f76
- <778b9dda4b24005a27bcd9c35c110bf8d7f259ca
- =<6.18.*
- =<7.0.*
- =<6.12.*
- <07ffe414a708ae60551401cec5d727ed156b8caf
- <5.9
- =<7.1.*
- =<6.1.*
- <511d2b92f8d20de04acafab676150d26fb5c67f4
- =<6.6.*
- =<*
- <10fc708b4de7f86002d2d735a2dbf3b5b7f65692
- ==5.9
- <ccdf4510a3873b14e5e348cdb038717996f09fda
- <3d205fe80f2181f0109150ad1fa06ee5bc046935