CVE-2025-39724None▾ SunlitIn 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 RB…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 2.8 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Oct 15.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.2%
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
Linux >= c49436b657d0a56a6ad90d14a7c3041add7cf64d < 0b882f00655afefbc7729c6b5aec86f7a5473a3dLinux >= c49436b657d0a56a6ad90d14a7c3041add7cf64d < b8ca8e3f75ede308b4d49a6ca5081460be01bdb5Linux >= c49436b657d0a56a6ad90d14a7c3041add7cf64d < 68c4613e89f000e8198f9ace643082c697921c9fLinux >= c49436b657d0a56a6ad90d14a7c3041add7cf64d < c826943abf473a3f7260fbadfad65e44db475460Linux >= c49436b657d0a56a6ad90d14a7c3041add7cf64d < cb7b3633ed749db8e56f475f43c960652cbd6882Linux >= c49436b657d0a56a6ad90d14a7c3041add7cf64d < 8e2739478c164147d0774802008528d9e03fb802Linux >= c49436b657d0a56a6ad90d14a7c3041add7cf64d < 38c0ea484dedb58cb3a4391229933e16be0d1031Linux >= c49436b657d0a56a6ad90d14a7c3041add7cf64d < 7f8fdd4dbffc05982b96caf586f77a014b2a9353Linux 6d5e79331417886196cb3a733bdb6645ba85bc42Linux 2401577586898b3590db80f8b97a26f81f0f6d4eLinux >= 3.10.48 < 3.11Linux >= 3.12.24 < 3.13Linux 3.13Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99118Nonedrm/i915/dmc: Harden DMC firmware payload parsing
CVE-2026-99117Nonenet: bridge: mcast: don't truncate the port group walk on teardown
CVE-2026-99121Noneipv4: avoid divide by zero in fib_rebalance
CVE-2026-99120NoneKVM: x86/mmu: Cope with the SS bit being set in #NPF exit codes
CVE-2026-99119Nonedrm/amdgpu/userq: actually validate userq BOs
CVE-2026-99123Nonevsock/virtio: validate packet source for connected sockets