Answer in brief
CVE-2023-54220 records a Unknown severity vulnerability in serial: 8250: Fix oops for port->pm on uart_change_pm(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2023-54220 records a Unknown severity vulnerability in serial: 8250: Fix oops for port->pm on uart_change_pm(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | 6.4 | Not reported |
| Linux/Linuxgeneric | >=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 | 66f3e55960698c874b0598277913b478ecd29573, 720a297b334e85d34099e83d1f375b92c3efedd6, b653289ca6460a6552c8590b75dfa84a0140a46b, bd70d0b28010d560a8be96b44fea86fe2ba016ae, 18e27df4f2b4e257c317ba8076f31a888f6cc64b, 0c05493341d6f2097f75f0a5dbb7b53a9e8c5f6c, 375806616f8c772c33d40e112530887b37c1a816, dfe2aeb226fd5e19b0ee795f4f6ed8bc494c1534, 4.14.324, 4.19.293, 5.4.255, 5.10.192, 5.15.128, 6.1.47, 6.4 |
Published upstream
Dec 30, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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().
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | 6.4 | Not reported |
| Linux/Linuxgeneric | >=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 | 66f3e55960698c874b0598277913b478ecd29573, 720a297b334e85d34099e83d1f375b92c3efedd6, b653289ca6460a6552c8590b75dfa84a0140a46b, bd70d0b28010d560a8be96b44fea86fe2ba016ae, 18e27df4f2b4e257c317ba8076f31a888f6cc64b, 0c05493341d6f2097f75f0a5dbb7b53a9e8c5f6c, 375806616f8c772c33d40e112530887b37c1a816, dfe2aeb226fd5e19b0ee795f4f6ed8bc494c1534, 4.14.324, 4.19.293, 5.4.255, 5.10.192, 5.15.128, 6.1.47, 6.4 |
Published upstream
Dec 30, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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().
Quoted source text, attributed separately from HOL analysis.