CVE-2026-23115
Race Condition in Linux Kernel Serial Driver Causes Kernel Crash
Publication date: 2026-02-14
Last updated on: 2026-03-18
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | From 6.15 (inc) to 6.18.8 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-362 | The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a race condition in the Linux kernel's serial driver related to the tty->port configuration. A commit that removed the call to tty_port_link_device() was reverted because that call is necessary to link the tty port before configuring it with uart_configure_port(). Without this link, user-space can open the console without the TTY being properly linked to the driver, which can cause kernel warnings and potentially crashes.
The issue occurs because the tty->port is not set before uart_configure_port() is called, leading to a race condition. This was reproducible on Qualcomm SoCs with fast boot and certain serial devices used as consoles, causing kernel warnings and instability.
How can this vulnerability impact me? :
This vulnerability can cause kernel warnings and potentially crash the kernel due to the tty->port not being set correctly before the console is opened. This can lead to system instability, especially on devices using Qualcomm SoCs with fast boot sequences and serial devices as consoles.
If exploited or triggered, it could disrupt normal system operation, causing unexpected reboots or failures in the console interface, which may impact system reliability and availability.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by observing kernel warning messages related to the tty port race condition. Specifically, look for messages like "tty_init_dev: ttyMSM driver does not set tty->port. This would crash the kernel. Fix the driver!" in the kernel logs.
To detect this on your system, you can check the kernel log for these warnings using commands such as:
- dmesg | grep 'tty_init_dev'
- journalctl -k | grep 'tty_init_dev'
- grep 'tty_init_dev' /var/log/kern.log
These commands will help identify if the race condition warning is present, indicating the vulnerability.
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to ensure that the tty->port is properly set before calling uart_configure_port(). This involves reverting any commits that removed the necessary tty_port_link_device() call, as this function links the tty and port to avoid the race condition.
In practice, this means applying the fix that reverts the offending commit bfc467db60b7 and restores the call to tty_port_link_device() in the serial driver code.
Additionally, monitor kernel logs for the warning message and avoid using affected serial drivers or devices until the fix is applied.