CVE-2025-39724
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
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or โ if you've already worked around this in production โ publish your fix to the community-verified tier.
โ Propose a mitigation on Community โ Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
| OS | Version | Status | Fixed in |
|---|---|---|---|
| sles | affected | | |
| debian | bookworm | fixed | 6.1.153-1 |
| debian | bullseye | fixed | 5.10.244-1 |
| debian | forky | fixed | 6.16.5-1 |
| debian | sid | fixed | 6.16.5-1 |
| debian | trixie | fixed | 6.12.48-1 |
| linux-kernel | affected | 3.11 | |
| debian | 11.0 | affected | |
References
- https://git.kernel.org/stable/c/0b882f00655afefbc7729c6b5aec86f7a5473a3d
- https://git.kernel.org/stable/c/38c0ea484dedb58cb3a4391229933e16be0d1031
- https://git.kernel.org/stable/c/68c4613e89f000e8198f9ace643082c697921c9f
- https://git.kernel.org/stable/c/7f8fdd4dbffc05982b96caf586f77a014b2a9353
- https://git.kernel.org/stable/c/8e2739478c164147d0774802008528d9e03fb802
- https://git.kernel.org/stable/c/b8ca8e3f75ede308b4d49a6ca5081460be01bdb5
- https://git.kernel.org/stable/c/c826943abf473a3f7260fbadfad65e44db475460
- https://git.kernel.org/stable/c/cb7b3633ed749db8e56f475f43c960652cbd6882
- https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html
- https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://www.suse.com/security/cve/CVE-2025-39724.html
- https://security-tracker.debian.org/tracker/CVE-2025-39724
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.