Local use-after-free via skipped UART cleanup
Published Feb 23, 2024 · Updated May 23, 2026
Use-after-free in the Linux 8250 OMAP UART driver in affected kernel releases allows local users to cause unspecified impact during device removal. The driver remove callback returns immediately when pm_runtime_resume_and_get() fails, skipping serial8250_unregister_port() and other cleanup while the core still removes the device. Reachability requires an OMAP UART using this driver, a device-removal path, and a runtime-resume failure; published evidence establishes leaked resources and a potential dangling UART object but no demonstrated exploit outcome.
Summary
What happened
Use-after-free in the Linux 8250 OMAP UART driver in affected kernel releases allows local users to cause unspecified impact during device removal. The driver remove callback returns immediately when pm_runtime_resume_and_get() fails, skipping serial8250_unregister_port() and other cleanup while the core still removes the device. Reachability requires an OMAP UART using this driver, a device-removal path, and a runtime-resume failure; published evidence establishes leaked resources and a potential dangling UART object but no demonstrated exploit outcome.
The record
- CVE
- CVE-2023-52457
- Published
- Feb 23, 2024
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 23, 2024CVE publishedPublication date reported by the CVE source.
- May 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=02eed6390dbe61115f3e3f63829c95c611aee67b
- Affected versionversion=2d66412563ef8953e2bac2d98d2d832b3f3f49cd <b502fb43f7fb55aaf07f6092ab44657595214b93
- Affected versionversion=5.10.156 <5.10.209
- Affected versionversion=5.15.80 <5.15.148
- Affected versionversion=5.4.225 <5.4.268
- Affected versionversion=6.0.10 <6.1
- Affected versionversion=6.1
- Affected versionversion=d833cba201adf9237168e19f0d76e4d7aa69f303 <bc57f3ef8a9eb0180606696f586a6dcfaa175ed0
- Affected versionversion=e0db709a58bdeb8966890882261a3f8438c5c9b7 <828cd829483f0cda920710997aed79130b0af690
- Affected versionversion=e3f0c638f428fd66b5871154b62706772045f91a <887a558d0298d36297daea039954c39940228d9b
- Affected versionversion=e3f0c638f428fd66b5871154b62706772045f91a <95e4e0031effad9837af557ecbfd4294a4d8aeee
- Affected versionversion=e3f0c638f428fd66b5871154b62706772045f91a <ad90d0358bd3b4554f243a425168fc7cebe7d04e
- Affected versionversion=e3f0c638f428fd66b5871154b62706772045f91a <d74173bda29aba58f822175d983d07c8ed335494
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo