CVE-2026-99455

published 19 Nov 2026 · updated 21 Nov 2026

serial: core: shut down initialized port on removal

4.4MediumCVSS 4.4EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel b05d5ed61e84ad15536e4e51db79a1d1c221c6f1, Kernel 0f332cce4d592d751aad89b404f68463099167c8, Kernel 810d467c11f0c85107874d08dfdd11acba6aa0c0 and 4 more.

In the Linux kernel, the following vulnerability has been resolved: serial: core: shut down initialized port on removal When a serial port configured as a console is opened and subsequently closed, tty_port_shutdown() skips invoking port->ops->shutdown() because port->console is true. As a result, tty_port_initialized() remains true and the port's interrupt handler stays registered in the irq subsystem. If the underlying device is later unbound or removed (e.g. via sysfs driver unbind or device hot-unplug), serial_core_remove_one_port() unregisters the console, frees uport->name via kfree(), and tears down the port without shutting it down or freeing its IRQ. Consequently, the irqaction descriptor remains registered in genirq with action->name pointing to freed memory. This triggers a use-after-free read whenever genirq accesses action->name, such as when reading /proc/interrupts: BUG: KASAN: slab-use-after-free in string+0x476/0x570 Call Trace: string+0x476/0x570 vsnprintf+0x422/0x1300 seq_printf+0x... show_interrupts+... Fix this by acquiring port->mutex in serial_core_remove_one_port() after console unregistration, clearing port->console under the mutex to prevent data races with concurrent tty_port_shutdown(), and invoking uart_shutdown(NULL, state) if the port remains initialized. This ensures that port->ops->shutdown() is called and the IRQ is freed before kfree(uport->name).

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=761ed4a94582ab291aa24dcbea4e01e8936488c8 <b05d5ed61e84ad15536e4e51db79a1d1c221c6f1, >=761ed4a94582ab291aa24dcbea4e01e8936488c8 <0f332cce4d592d751aad89b404f68463099167c8, >=761ed4a94582ab291aa24dcbea4e01e8936488c8 <810d467c11f0c85107874d08dfdd11acba6aa0c0, >=761ed4a94582ab291aa24dcbea4e01e8936488c8 <928335263daf58e8c0e14d860091e57791693ea0, =4.9b05d5ed61e84ad15536e4e51db79a1d1c221c6f1, 0f332cce4d592d751aad89b404f68463099167c8, 810d467c11f0c85107874d08dfdd11acba6aa0c0, 928335263daf58e8c0e14d860091e57791693ea0
linux-kernel: Kernel>=6.13.0 <6.18.61, >=6.19.0 <7.3.2, >=4.9.0 <6.12.1176.18.61, 7.3.2, 6.12.117

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-99455 severity on Zeptric[![CVE-2026-99455](https://zeptric.io/badge/cve/CVE-2026-99455.svg)](https://zeptric.io/cve/CVE-2026-99455)