CVE-2026-99455
serial: core: shut down initialized port on removal
What happened?
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 software and versions
| Software | Version information | Fixed version |
|---|---|---|
| LinuxLinux | affected: 761ed4a94582ab291aa24dcbea4e01e8936488c8 to < b05d5ed61e84ad15536e4e51db79a1d1c221c6f1; affected: 761ed4a94582ab291aa24dcbea4e01e8936488c8 to < 0f332cce4d592d751aad89b404f68463099167c8; affected: 761ed4a94582ab291aa24dcbea4e01e8936488c8 to < 928335263daf58e8c0e14d860091e57791693ea0; affected: 761ed4a94582ab291aa24dcbea4e01e8936488c8 to < 810d467c11f0c85107874d08dfdd11acba6aa0c0 | See vendor advisory |
| LinuxLinux | affected: 4.9; unaffected: 0 to < 4.9; unaffected: 6.12.117 to ≤ 6.12.*; unaffected: 6.18.61 to ≤ 6.18.*; unaffected: 7.3.2 to ≤ 7.3.*; unaffected: 7.4-rc1 to ≤ * | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.
Sources and remediation references
- https://www.cve.org/CVERecord?id=CVE-2026-99455
- https://git.kernel.org/stable/c/b05d5ed61e84ad15536e4e51db79a1d1c221c6f1
- https://git.kernel.org/stable/c/0f332cce4d592d751aad89b404f68463099167c8
- https://git.kernel.org/stable/c/928335263daf58e8c0e14d860091e57791693ea0
- https://git.kernel.org/stable/c/810d467c11f0c85107874d08dfdd11acba6aa0c0