CVE-2023-54220: serial: 8250: Fix oops for port->pm on uart_change_pm()
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0c05493341d6f2097f75f0a5dbb7b53a9e8c5f6c, 18e27df4f2b4e257c317ba8076f31a888f6cc64b, 375806616f8c772c33d40e112530887b37c1a816.
Low priority for now. Upgrade to Linux Linux 0c05493341d6f2097f75f0a5dbb7b53a9e8c5f6c, 18e27df4f2b4e257c317ba8076f31a888f6cc64b, 375806616f8c772c33d40e112530887b37c1a816 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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().
- Published
- Dec 30, 2025
- Updated
- Oct 28, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- —
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 8e596aed5f2f98cf3e6e98d6fe1d689f4a319308, 6.4affected
- 490bf37eaabb0a857ed1ae8e75d8854e41662f1c and later · before 66f3e55960698c874b0598277913b478ecd29573affected · git
- c9e080c3005fd183c56ff8f4d75edb5da0765d2c and later · before 720a297b334e85d34099e83d1f375b92c3efedd6affected · git
- d5cd2928d31042a7c0a01464f9a8d95be736421d and later · before b653289ca6460a6552c8590b75dfa84a0140a46baffected · git
- 2c86a1305c1406f45ea780d06953c484ea1d9e6e and later · before bd70d0b28010d560a8be96b44fea86fe2ba016aeaffected · git
- 1ba5594739d858e524ff0f398ee1ebfe0a8b9d41 and later · before 18e27df4f2b4e257c317ba8076f31a888f6cc64baffected · git
- af4d6dbb1a92ea424ad1ba1d0c88c7fa2345d872 and later · before 0c05493341d6f2097f75f0a5dbb7b53a9e8c5f6caffected · git
- 04e82793f068d2f0ffe62fcea03d007a8cdc16a7 and later · before 375806616f8c772c33d40e112530887b37c1a816affected · git
- 04e82793f068d2f0ffe62fcea03d007a8cdc16a7 and later · before dfe2aeb226fd5e19b0ee795f4f6ed8bc494c1534affected · git
- 4.14.316 and later · before 4.14.324affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.52-1 | 6.1.52-1 |
| Debian:13 | linux | before 6.4.13-1 | 6.4.13-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2023-54218Dec 30, 2025 · net: Fix load-tearing on sk->sk_stamp in sock_recv_cmsgs().0Monitor
- ← EarlierCVE-2023-54219Dec 30, 2025 · Revert "IB/isert: Fix incorrect release of isert connection"30Monitor
- Later →CVE-2023-54221Dec 30, 2025 · clk: imx93: fix memory leak and missing unwind goto in imx93_clocks_probe0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0c05493341d6f2097f75f0a5dbb7b53a9e8c5f6c | Vendor (CNA) |
| Linux Linux | 18e27df4f2b4e257c317ba8076f31a888f6cc64b | Vendor (CNA) |
| Linux Linux | 375806616f8c772c33d40e112530887b37c1a816 | Vendor (CNA) |
| Linux Linux | 4.14.324 | Vendor (CNA) |
| Linux Linux | 4.19.293 | Vendor (CNA) |
| Linux Linux | 5.10.192 | Vendor (CNA) |
| Linux Linux | 5.15.128 | Vendor (CNA) |
| Linux Linux | 5.4.255 | Vendor (CNA) |
| Linux Linux | 6.1.47 | Vendor (CNA) |
| Linux Linux | 6.4 | Vendor (CNA) |
| Linux Linux | 66f3e55960698c874b0598277913b478ecd29573 | Vendor (CNA) |
| Linux Linux | 720a297b334e85d34099e83d1f375b92c3efedd6 | Vendor (CNA) |
| Linux Linux | b653289ca6460a6552c8590b75dfa84a0140a46b | Vendor (CNA) |
| Linux Linux | bd70d0b28010d560a8be96b44fea86fe2ba016ae | Vendor (CNA) |
| Linux Linux | dfe2aeb226fd5e19b0ee795f4f6ed8bc494c1534 | Vendor (CNA) |
| debian:linux | 6.1.52-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/18e27df4f2b4e257c317ba8076f31a888f6cc64b
- git.kernel.org/stable/c/375806616f8c772c33d40e112530887b37c1a816
- git.kernel.org/stable/c/66f3e55960698c874b0598277913b478ecd29573
- git.kernel.org/stable/c/720a297b334e85d34099e83d1f375b92c3efedd6
- git.kernel.org/stable/c/b653289ca6460a6552c8590b75dfa84a0140a46b
- git.kernel.org/stable/c/bd70d0b28010d560a8be96b44fea86fe2ba016ae
- git.kernel.org/stable/c/dfe2aeb226fd5e19b0ee795f4f6ed8bc494c1534
Vendor advisories and official records. Exploit/PoC links are deliberately left out.