CVE-2023-54220

serial: 8250: Fix oops for port->pm on uart_change_pm()

HIGH
7.8
CVSS Score
Published: December 30, 2025 at 12:11 PM UTC
Updated: October 28, 2026 at 07:10 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: serial: 8250: Fix oops for port->pm on uart_change_pm() Unloading a hardware specific 8250 driver can produce error "Unable to handle kernel paging request at virtual address" about ten seconds after unloading the driver. This happens on uart_hangup() calling uart_change_pm(). Turns out commit 04e82793f068 ("serial: 8250: Reinit port->pm on port specific driver unbind") was only a partial fix. If the hardware specific driver has initialized port->pm function, we need to clear port->pm too. Just reinitializing port->ops does not do this. Otherwise serial8250_pm() will call port->pm() instead of serial8250_do_pm().

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

04e82793f068d2f0ffe62fcea03d007a8cdc16a71ba5594739d858e524ff0f398ee1ebfe0a8b9d412c86a1305c1406f45ea780d06953c484ea1d9e6e4.14.3164.19.284490bf37eaabb0a857ed1ae8e75d8854e41662f1c4e82793f68d2f0ffe62fcea3d7a8cdc16a75.10.1815.15.1135.4.2446.1.306.3.46.48e596aed5f2f98cf3e6e98d6fe1d689f4a319308af4d6dbb1a92ea424ad1ba1d0c88c7fa2345d872c9e080c3005fd183c56ff8f4d75edb5da0765d2cd5cd2928d31042a7c0a01464f9a8d95be736421d
Vendor states this is fixed in 0c05493341d6f2097f75f0a5dbb7b53a9e8c5f6c (fixed)
Vendor states this is fixed in 18e27df4f2b4e257c317ba8076f31a888f6cc64b (fixed)
Vendor states this is fixed in 375806616f8c772c33d40e112530887b37c1a816 (fixed)
Vendor states this is fixed in 66f3e55960698c874b0598277913b478ecd29573 (fixed)
Vendor states this is fixed in 720a297b334e85d34099e83d1f375b92c3efedd6 (fixed)
Vendor states this is fixed in b653289ca6460a6552c8590b75dfa84a0140a46b (fixed)
Vendor states this is fixed in bd70d0b28010d560a8be96b44fea86fe2ba016ae (fixed)
Vendor states this is fixed in dfe2aeb226fd5e19b0ee795f4f6ed8bc494c1534 (fixed)
Vendor states this is fixed in 4.14.324 (unaffected)
Vendor states this is fixed in 4.19.293 (unaffected)
Vendor states this is fixed in 5.10.192 (unaffected)
Vendor states this is fixed in 5.15.128 (unaffected)
Vendor states this is fixed in 5.4.255 (unaffected)
Vendor states this is fixed in 6.1.47 (unaffected)
Vendor states this is fixed in 6.4 (unaffected)
Vendor states this is fixed in 6.4.12 (unaffected)
Vendor states this is fixed in 6.5 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card