CVE-2026-43124

pstore: ram_core: fix incorrect success return when vmap() fails

MEDIUM
5.5
CVSS Score
Published: May 6, 2026 at 11:27 AM UTC
Updated: June 17, 2026 at 10:48 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.1%

Description

In the Linux kernel, the following vulnerability has been resolved: pstore: ram_core: fix incorrect success return when vmap() fails In persistent_ram_vmap(), vmap() may return NULL on failure. If offset is non-zero, adding offset_in_page(start) causes the function to return a non-NULL pointer even though the mapping failed. persistent_ram_buffer_map() therefore incorrectly returns success. Subsequent access to prz->buffer may dereference an invalid address and cause crashes. Add proper NULL checking for vmap() failures.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 3.16.62v ≥ 3.18.123v ≥ 4.14.72v ≥ 4.18.10v ≥ 4.4.158v ≥ 4.9.1293.16.62 ≤ v < 3.173.16.62 ≤ v < 5.10.2523.18.123 ≤ v < 3.194.14.72 ≤ v < 4.154.18.10 ≤ v < 4.194.19 ≤ v < 5.10.2524.19 ≤ v < 5.15.2024.19 ≤ v < 6.1.1654.19 ≤ v < 6.12.754.19 ≤ v < 6.18.164.19 ≤ v < 6.19.64.19 ≤ v < 6.6.1284.19 ≤ v < 7.04.4.158 ≤ v < 4.54.9.129 ≤ v < 4.105.11 ≤ v < 5.15.2025.16 ≤ v < 6.1.1656.13 ≤ v < 6.18.166.19 ≤ v < 6.19.66.2 ≤ v < 6.6.1286.7 ≤ v < 6.12.751cd01dba1355e291f636555b1920625ed58c16231e5b387747ba285a64348b9a96b246d0b9d52b033.16.623.18.12336a9916189b46b78dbf4fa542739b464444f05374.14.724.18.104.194.4.1584.9.1297026e2457c5b0c0e8a81e65a8209b8420a437b4d831b624df1b420c8f9281ed1307a8db23afb72df9095f19baae92afb978f8df77d19280fe291b337d0028f48b33086cf6d8f87831a650866107b5785
Vendor states this is fixed in 05363abc7625cf18c96e67f50673cd07f11da5e9 (fixed)
Vendor states this is fixed in 1da904e84de608907662ad8a51ba9c571d61e003 (fixed)
Vendor states this is fixed in 2c99326dc1c79b7ce3c8dd92929b5ce724ff70eb (fixed)
Vendor states this is fixed in 49918dd52615097529811d21ec6074dd02ebe77c (fixed)
Vendor states this is fixed in 88d5b28f63c7aac1271784e3b800ed405d1cde75 (fixed)
Vendor states this is fixed in 8baa234181f632cabacf73e4834a910859e9fcc9 (fixed)
Vendor states this is fixed in 8d849adfbc3e98417fb541620568db1a759ef441 (fixed)
Vendor states this is fixed in d47234840aeb4182ed3ee795c578b1dfa9cbd25b (fixed)
Affected range stops below 3.17, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.19, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.10, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.15, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 4.19 (unaffected)
Affected range stops below 4.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.10.252 (unaffected)
Vendor states this is fixed in 5.15.202 (unaffected)
Vendor states this is fixed in 6.1.165 (unaffected)
Vendor states this is fixed in 6.12.75 (unaffected)
Vendor states this is fixed in 6.18.16 (unaffected)
Vendor states this is fixed in 6.19.6 (unaffected)
Vendor states this is fixed in 6.6.128 (unaffected)
Vendor states this is fixed in 7.0 (unaffected)

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-476

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card