Kernel crash via offset-adjusted NULL mapping
Published May 6, 2026 · Updated May 6, 2026
NULL pointer dereference in Linux Kernel pstore ram_core allows local users to crash the kernel after a failed persistent RAM mapping. persistent_ram_vmap() adds a nonzero page offset to a NULL vmap() result, so persistent_ram_buffer_map() reports success and leaves prz->buffer invalid. A low-privileged local user must reach the pstore persistent-RAM path; later buffer access can crash the operating system without reported data disclosure or modification.
Summary
What happened
NULL pointer dereference in Linux Kernel pstore ram_core allows local users to crash the kernel after a failed persistent RAM mapping. persistent_ram_vmap() adds a nonzero page offset to a NULL vmap() result, so persistent_ram_buffer_map() reports success and leaves prz->buffer invalid. A low-privileged local user must reach the pstore persistent-RAM path; later buffer access can crash the operating system without reported data disclosure or modification.
The record
- CVE
- CVE-2026-43124
- Published
- May 6, 2026
- Updated
- May 6, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 6, 2026CVE publishedPublication date reported by the CVE source.
- May 6, 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <05363abc7625cf18c96e67f50673cd07f11da5e9
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1da904e84de608907662ad8a51ba9c571d61e003
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2c99326dc1c79b7ce3c8dd92929b5ce724ff70eb
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <49918dd52615097529811d21ec6074dd02ebe77c
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <88d5b28f63c7aac1271784e3b800ed405d1cde75
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8baa234181f632cabacf73e4834a910859e9fcc9
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8d849adfbc3e98417fb541620568db1a759ef441
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d47234840aeb4182ed3ee795c578b1dfa9cbd25b
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