Skip to content
Threat Brief

← All advisories

CVE-2026-99455

Severity unknownNo known exploitationFix available

serial: core: shut down initialized port on removal

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 6% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

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).

Patching and mitigation

Patch status
Fix available (source: CVE record (Linux))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 761ed4a94582ab291aa24dcbea4e01e8936488c8 before 0f332cce4d592d751aad89b404f68463099167c80f332cce4d592d751aad89b404f68463099167c8CVE Program
LinuxLinuxfrom 761ed4a94582ab291aa24dcbea4e01e8936488c8 before 928335263daf58e8c0e14d860091e57791693ea0928335263daf58e8c0e14d860091e57791693ea0CVE Program
LinuxLinuxfrom 761ed4a94582ab291aa24dcbea4e01e8936488c8 before 810d467c11f0c85107874d08dfdd11acba6aa0c0810d467c11f0c85107874d08dfdd11acba6aa0c0CVE Program
LinuxLinuxfrom 761ed4a94582ab291aa24dcbea4e01e8936488c8 before b05d5ed61e84ad15536e4e51db79a1d1c221c6f1b05d5ed61e84ad15536e4e51db79a1d1c221c6f1CVE Program
LinuxLinux4.9Not documentedCVE Program
LinuxLinux (unaffected)from 6.12.117 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.61 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.3.2 up to and including 7.3.*Not documentedCVE Program
LinuxLinux (unaffected)7.4-rc1Not documentedCVE Program
LinuxLinux (unaffected)all versions before 4.9Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (Linux)

    Source: CVE record (Linux) (opens in a new tab)

Vendor guidance and references