High 7.8Published Sep 15, 2025

CVE-2023-53176serial: 8250: Reinit port->pm on port specific driver unbind

Updated under an hour ago (Oct 26, 2026, 2:50 PM ET)

Does this affect you?

It affects Linux and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for Linux

Exploited in the last 30 days

In the Linux kernel, the following vulnerability has been resolved: serial: 8250: Reinit port->pm on port specific driver unbind When we unbind a serial port hardware specific 8250 driver, the generic serial8250 driver takes over the port. After that we see an oops about 10 seconds later. This can produce the following at least on some TI SoCs: Unhandled fault: imprecise external abort (0x1406) Internal error: : 1406 [#1] SMP ARM Turns out that we may still have the serial port hardware specific driver port->pm in use, and serial8250_pm() tries to call it after the port specific driver is gone: serial8250_pm [8250_base] from uart_change_pm+0x54/0x8c [serial_base] uart_change_pm [serial_base] from uart_hangup+0x154/0x198 [serial_base] uart_hangup [serial_base] from __tty_hangup.part.0+0x328/0x37c __tty_hangup.part.0 from disassociate_ctty+0x154/0x20c disassociate_ctty from do_exit+0x744/0xaac do_exit from do_group_exit+0x40/0x8c do_group_exit from __wake_up_parent+0x0/0x1c Let's fix the issue by calling serial8250_set_defaults() in serial8250_unregister_port(). This will set the port back to using the serial8250 default functions, and sets the port->pm to point to serial8250_pm.

CVSS: 7.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness (CWE): Not given
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: Linux
NVD analysis: Modified
Record last updated: Oct 15, 2026
First seen by InfoSec Signals: Oct 15, 2026

Affected products

Affected products

Linux Linux linux:linux (from the name)	from c161afe9759ddcc174d08e7c4f683d08ac9ba86f before 490bf37eaabb0a857ed1ae8e75d8854e41662f1c; from c161afe9759ddcc174d08e7c4f683d08ac9ba86f before c9e080c3005fd183c56ff8f4d75edb5da0765d2c; from c161afe9759ddcc174d08e7c4f683d08ac9ba86f before d5cd2928d31042a7c0a01464f9a8d95be736421d; from c161afe9759ddcc174d08e7c4f683d08ac9ba86f before 2c86a1305c1406f45ea780d06953c484ea1d9e6e; from c161afe9759ddcc174d08e7c4f683d08ac9ba86f before 1ba5594739d858e524ff0f398ee1ebfe0a8b9d41; from c161afe9759ddcc174d08e7c4f683d08ac9ba86f before af4d6dbb1a92ea424ad1ba1d0c88c7fa2345d872; from c161afe9759ddcc174d08e7c4f683d08ac9ba86f before 8e596aed5f2f98cf3e6e98d6fe1d689f4a319308; from c161afe9759ddcc174d08e7c4f683d08ac9ba86f before 04e82793f068d2f0ffe62fcea03d007a8cdc16a7	CNA record
linux linux_kernel linux:linux_kernel	before 4.14.316; from 4.15 before 4.19.284; from 4.20 before 5.4.244; from 5.5 before 5.10.181; from 5.11 before 5.15.113; from 5.16 before 6.1.30; from 6.2 before 6.3.4	NVD

References

References

https://git.kernel.org/stable/c/490bf37eaabb0a857ed1ae8e75d8854e41662f1c	patch
https://git.kernel.org/stable/c/c9e080c3005fd183c56ff8f4d75edb5da0765d2c	patch
https://git.kernel.org/stable/c/d5cd2928d31042a7c0a01464f9a8d95be736421d	patch
https://git.kernel.org/stable/c/2c86a1305c1406f45ea780d06953c484ea1d9e6e	patch
https://git.kernel.org/stable/c/1ba5594739d858e524ff0f398ee1ebfe0a8b9d41	patch
https://git.kernel.org/stable/c/af4d6dbb1a92ea424ad1ba1d0c88c7fa2345d872	patch
https://git.kernel.org/stable/c/8e596aed5f2f98cf3e6e98d6fe1d689f4a319308	patch
https://git.kernel.org/stable/c/04e82793f068d2f0ffe62fcea03d007a8cdc16a7	patch

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.