Skip to main content
VulnerabilityPublished Updated

CVE-2026-43124: Linux kernel · pstore: ram_core: fix incorrect success return when vmap() fails

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in d47234840aeb4182ed3ee795c578b1dfa9cbd25b : patch Linux kernel soon.

Data as of 6 Nov 2026, 16:04 UTC

Severity
High

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

  1. Disclosed: evidence found.

    CVE published 6 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
LinuxLinuxAffected
  • >=3.16.62 <3.17
  • >=3.18.123 <3.19
  • >=4.4.158 <4.5
  • >=4.9.129 <4.10
  • >=4.14.72 <4.15
  • >=4.18.10 <4.19
Fixed in
  • d47234840aeb4182ed3ee795c578b1dfa9cbd25b
  • 49918dd52615097529811d21ec6074dd02ebe77c
  • 05363abc7625cf18c96e67f50673cd07f11da5e9
  • 88d5b28f63c7aac1271784e3b800ed405d1cde75
  • 8d849adfbc3e98417fb541620568db1a759ef441
  • 8baa234181f632cabacf73e4834a910859e9fcc9
  • 4.19
  • 4.15
  • 4.10
  • 4.5
  • 3.19
  • 3.17
  • 2c99326dc1c79b7ce3c8dd92929b5ce724ff70eb
  • 1da904e84de608907662ad8a51ba9c571d61e003
LinuxLinuxAffected
  • =4.19
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

Community reviews

Loading reviews…