CVE-2026-43124: Linux kernel · pstore: ram_core: fix incorrect success return when vmap() fails
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in d47234840aeb4182ed3ee795c578b1dfa9cbd25b : patch Linux kernel soon.
Data as of 6 Nov 2026, 16:04 UTC
Rated High by Threat Radar's AI analysis · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-06.
- Patch
- Available – fixed in d47234840aeb4182ed3ee795c578b1dfa9cbd25b, 49918dd52615097529811d21ec6074dd02ebe77c, 05363abc7625cf18c96e67f50673cd07f11da5e9 +11
Exploitation evidence
Disclosed: evidence found.
CVE published 6 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available in Linux kernel versions 4.5, 4.10, 4.15, and 4.19 and corresponding commits. Users should update to these fixed versions or later to mitigate this issue.
Description
A vulnerability in the Linux kernel's pstore ram_core component causes persistent_ram_buffer_map() to incorrectly return success when vmap() fails, potentially leading to invalid memory dereferences and system crashes. This occurs because persistent_ram_vmap() may return a non-NULL pointer despite vmap() failure due to offset adjustments. The issue has been fixed by adding proper NULL checks for vmap() failures.
References
- git.kernel.org/stable/c/d47234840aeb4182ed3ee795c578b1dfa9cbd25b (opens in a new tab)
- git.kernel.org/stable/c/49918dd52615097529811d21ec6074dd02ebe77c (opens in a new tab)
- git.kernel.org/stable/c/8baa234181f632cabacf73e4834a910859e9fcc9 (opens in a new tab)
- git.kernel.org/stable/c/1da904e84de608907662ad8a51ba9c571d61e003 (opens in a new tab)
- git.kernel.org/stable/c/8d849adfbc3e98417fb541620568db1a759ef441 (opens in a new tab)
- git.kernel.org/stable/c/2c99326dc1c79b7ce3c8dd92929b5ce724ff70eb (opens in a new tab)
- git.kernel.org/stable/c/88d5b28f63c7aac1271784e3b800ed405d1cde75 (opens in a new tab)
- git.kernel.org/stable/c/05363abc7625cf18c96e67f50673cd07f11da5e9 (opens in a new tab)