System crash via unaligned pstore zone mapping
Published Mar 18, 2024 · Updated May 11, 2026
Denial of service in affected Linux kernel releases allows local users to crash the system by initializing pstore/ram with an odd CPU count. The pstore/ram initialization path divides reserved memory into per-CPU zones without forcing an even zone size, so odd-numbered zones receive unaligned virtual addresses that crash when accessed. The pstore RAM backend must be enabled and initialized with an odd maximum CPU count; the reported consequence is a local system crash without disclosed data access or modification.
Summary
What happened
Denial of service in affected Linux kernel releases allows local users to crash the system by initializing pstore/ram with an odd CPU count. The pstore/ram initialization path divides reserved memory into per-CPU zones without forcing an even zone size, so odd-numbered zones receive unaligned virtual addresses that crash when accessed. The pstore RAM backend must be enabled and initialized with an odd maximum CPU count; the reported consequence is a local system crash without disclosed data access or modification.
The record
- CVE
- CVE-2023-52619
- Published
- Mar 18, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 18, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 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=4.10
- Affected versionversion=de83209249d64bad993f25d3ea4bba57683e2e2e <0593cfd321df9001142a9d2c58d4144917dff7ee
- Affected versionversion=de83209249d64bad993f25d3ea4bba57683e2e2e <2a37905d47bffec61e95d99f0c1cc5dc6377956c
- Affected versionversion=de83209249d64bad993f25d3ea4bba57683e2e2e <75b0f71b26b3ad833c5c0670109c0af6e021e86a
- Affected versionversion=de83209249d64bad993f25d3ea4bba57683e2e2e <8b69c30f4e8b69131d92096cb296dc1f217101e4
- Affected versionversion=de83209249d64bad993f25d3ea4bba57683e2e2e <a63e48cd835c34c38ef671d344cc029b1ea5bf10
- Affected versionversion=de83209249d64bad993f25d3ea4bba57683e2e2e <cd40e43f870cf21726b22487a95ed223790b3542
- Affected versionversion=de83209249d64bad993f25d3ea4bba57683e2e2e <d49270a04623ce3c0afddbf3e984cb245aa48e9c
- Affected versionversion=de83209249d64bad993f25d3ea4bba57683e2e2e <e9f6ac50890104fdf8194f2865680689239d30fb
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