CVE-2025-39724
Last modified
CVE-2025-39724 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: serial: 8250: fix panic due to PSLVERR When the PSLVERR_RESP_EN parameter is set to 1, the device generates an error response if an attempt is made to read an empty RBR (Receive Buffer Register) while the FIFO is enabled. In serial8250_do_startup(), calling serial_port_out(port, UART_LCR, UART_LCR_WLEN8) triggers dw8250_check_lcr(), which invokes dw8250_force_idle() and serial8250_clear_and_reinit_fifos(). The latter function enables the FIFO via serial_out(p, UART_FCR, p->fcr). Execution proceeds to the serial_port_in(port, UART_RX). This satisfies the PSLVERR trigger condition. When another CPU (e.g., using printk()) is accessing the UART (UART is busy), the current CPU fails the check (value & ~UART_LCR_SPAR) == (lcr & ~UART_LCR_SPAR) in dw8250_check_lcr(), causing it to enter dw8250_force_idle(). Put serial_port_out(port, UART_LCR, UART_LCR_WLEN8) under the port->lock to fix this issue. Panic backtrace: [ 0.442336] Oops - unknown exception [#1] [ 0.442343] epc : dw8250_serial_in32+0x1e/0x4a [ 0.442351] ra : serial8250_do_startup+0x2c8/0x88e ... [ 0.442416] console_on_rootfs+0x26/0x70. EPSS estimates a 0.16% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: serial: 8250: fix panic due to PSLVERR When the PSLVERR_RESP_EN parameter is set to 1, the device generates an error response if an attempt is made to read an empty RBR (Receive Buffer Register) while the FIFO is enabled. In serial8250_do_startup(), calling serial_port_out(port, UART_LCR, UART_LCR_WLEN8) triggers dw8250_check_lcr(), which invokes dw8250_force_idle() and serial8250_clear_and_reinit_fifos(). The latter function enables the FIFO via serial_out(p, UART_FCR, p->fcr). Execution proceeds to the serial_port_in(port, UART_RX). This satisfies the PSLVERR trigger condition. When another CPU (e.g., using printk()) is accessing the UART (UART is busy), the current CPU fails the check (value & ~UART_LCR_SPAR) == (lcr & ~UART_LCR_SPAR) in dw8250_check_lcr(), causing it to enter dw8250_force_idle(). Put serial_port_out(port, UART_LCR, UART_LCR_WLEN8) under the port->lock to fix this issue. Panic backtrace: [ 0.442336] Oops - unknown exception [#1] [ 0.442343] epc : dw8250_serial_in32+0x1e/0x4a [ 0.442351] ra : serial8250_do_startup+0x2c8/0x88e ... [ 0.442416] console_on_rootfs+0x26/0x70
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 3.10.48, < 3.11 |
| Linux | Linux Kernel | >= 3.12.24, < 5.4.297 |
| Linux | Linux Kernel | >= 5.5, < 5.10.241 |
| Linux | Linux Kernel | >= 5.11, < 5.15.190 |
| Linux | Linux Kernel | >= 5.16, < 6.1.149 |
| Linux | Linux Kernel | >= 6.2, < 6.6.103 |
| Linux | Linux Kernel | >= 6.7, < 6.12.44 |
| Linux | Linux Kernel | >= 6.13, < 6.16.4 |
| Debian | Debian Linux | 11.0 |
References
- https://lists.debian.org/debian-lts-announce/2025/10/msg00007.htmlMailing List, Third Party Advisory
- https://lists.debian.org/debian-lts-announce/2025/10/msg00008.htmlMailing List, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2025-39724?
How severe is CVE-2025-39724?
How do I fix CVE-2025-39724?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-39719In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2025-3972A vulnerability, which was classified as critical, has been …9.8
- CVE-2025-39720In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39721In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39722In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39723In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-39725In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39726In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2025-39727In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-39728In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39729In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-3973A vulnerability, which was classified as critical, was found…9.8
Are you affected by CVE-2025-39724?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
