serial: core: do fallible allocations before the console can be registered
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 1a0e4fbce5d9c1bc179a35a2fd9ed142664299e3, Kernel 8c7c75bfa7b84d6999de2100ce9c09e3779249a0, Kernel 9260a92ce90e6a95ce2ffdf1441c5216bf3f9552 and 3 more.
In the Linux kernel, the following vulnerability has been resolved: serial: core: do fallible allocations before the console can be registered serial_core_add_one_port() allocates uport->tty_groups after uart_configure_port(), which may register the console. If the allocation fails, the driver unwinds the port while its console remains registered. The earlier uport->name allocation has a related failure path that leaves state->uart_port linked to a port being freed. Failslab reproduced a NULL dereference in PL011 console output and a KASAN use-after-free in i.MX console output after failed binds. Allocate the name and tty_groups before linking the port and configuring it. Reserve space for the optional driver attribute group because config_port() may populate uport->attr_group during configuration.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =3.17, >=266dcff03eed0050b6af11aaf2a61ab837d7ba3f <1a0e4fbce5d9c1bc179a35a2fd9ed142664299e3, >=266dcff03eed0050b6af11aaf2a61ab837d7ba3f <8c7c75bfa7b84d6999de2100ce9c09e3779249a0, >=266dcff03eed0050b6af11aaf2a61ab837d7ba3f <9260a92ce90e6a95ce2ffdf1441c5216bf3f9552, >=266dcff03eed0050b6af11aaf2a61ab837d7ba3f <be61f56c4f0ed1cbf16c5f7b0dec6d6414993dd4, >=266dcff03eed0050b6af11aaf2a61ab837d7ba3f <c2aec15f78b2e6ccd9b94216a901248511355982, >=266dcff03eed0050b6af11aaf2a61ab837d7ba3f <e2ddbfd826836cba1b7a25ee4eb512f7d752b703 | 1a0e4fbce5d9c1bc179a35a2fd9ed142664299e3, 8c7c75bfa7b84d6999de2100ce9c09e3779249a0, 9260a92ce90e6a95ce2ffdf1441c5216bf3f9552, be61f56c4f0ed1cbf16c5f7b0dec6d6414993dd4, c2aec15f78b2e6ccd9b94216a901248511355982, e2ddbfd826836cba1b7a25ee4eb512f7d752b703 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket