SECUFOCUSNOW
Home›CVE index›CVE-2023-54220
Review reviewHigh

CVE-2023-54220

Linux

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...

CVSS
7.8
EPSS
0.13%
3.33% percentile
CISA KEV
Not listed
Published
2025.12.30
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.13%
Technical severityCVSS 7.8

Vulnerability overview

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...

Affected product and versions

Product
Linux
Affected versions
>= 490bf37eaabb0a857ed1ae8e75d8854e41662f1c < 66f3e55960698c874b0598277913b478ecd29573, >= c9e080c3005fd183c56ff8f4d75edb5da0765d2c < 720a297b334e85d34099e83d1f375b92c3efedd6, >= d5cd2928d31042a7c0a01464f9a8d95be736421d < b653289ca6460a6552c8590b75dfa84a0140a46b, >= 2c86a1305c1406f45ea780d06953c484ea1d9e6e < bd70d0b28010d560a8be96b44fea86fe2ba016ae, >= 1ba5594739d858e524ff0f398ee1ebfe0a8b9d41 < 18e27df4f2b4e257c317ba8076f31a888f6cc64b, >= af4d6dbb1a92ea424ad1ba1d0c88c7fa2345d872 < 0c05493341d6f2097f75f0a5dbb7b53a9e8c5f6c, >= 04e82793f068d2f0ffe62fcea03d007a8cdc16a7 < 375806616f8c772c33d40e112530887b37c1a816, >= 04e82793f068d2f0ffe62fcea03d007a8cdc16a7 < dfe2aeb226fd5e19b0ee795f4f6ed8bc494c1534, >= 8e596aed5f2f98cf3e6e98d6fe1d689f4a319308, >= 4.14.316 < 4.14.324, >= 4.19.284 < 4.19.293, >= 5.4.244 < 5.4.255, >= 5.10.181 < 5.10.192, >= 5.15.113 < 5.15.128, >= 6.1.30 < 6.1.47, >= 6.3.4 < 6.4, >= 6.4
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
Not available