Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 6 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-43124, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.13% · top 98% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 831b624df1b420c8f9281ed1307a8db23afb72df – < d47234840aeb4182ed3ee795c578b1dfa9cbd25b
    • affected 831b624df1b420c8f9281ed1307a8db23afb72df – < 49918dd52615097529811d21ec6074dd02ebe77c
    • affected 831b624df1b420c8f9281ed1307a8db23afb72df – < 8baa234181f632cabacf73e4834a910859e9fcc9
    • affected 831b624df1b420c8f9281ed1307a8db23afb72df – < 1da904e84de608907662ad8a51ba9c571d61e003
    • affected 831b624df1b420c8f9281ed1307a8db23afb72df – < 8d849adfbc3e98417fb541620568db1a759ef441
    • affected 831b624df1b420c8f9281ed1307a8db23afb72df – < 2c99326dc1c79b7ce3c8dd92929b5ce724ff70eb
    • affected 831b624df1b420c8f9281ed1307a8db23afb72df – < 88d5b28f63c7aac1271784e3b800ed405d1cde75
    • affected 831b624df1b420c8f9281ed1307a8db23afb72df – < 05363abc7625cf18c96e67f50673cd07f11da5e9
    • affected 9095f19baae92afb978f8df77d19280fe291b337
    • affected 36a9916189b46b78dbf4fa542739b464444f0537
    • affected 1cd01dba1355e291f636555b1920625ed58c1623
    • affected 7026e2457c5b0c0e8a81e65a8209b8420a437b4d
    • affected 1e5b387747ba285a64348b9a96b246d0b9d52b03
    • affected d0028f48b33086cf6d8f87831a650866107b5785
    • affected 3.16.62 – < 3.17
    • affected 3.18.123 – < 3.19
    • affected 4.4.158 – < 4.5
    • affected 4.9.129 – < 4.10
    • affected 4.14.72 – < 4.15
    • affected 4.18.10 – < 4.19
  • Linux · Linux

    • affected 4.19
    • unaffected < 4.19
    • unaffected 5.10.252 – ≤ 5.10.*
    • unaffected 5.15.202 – ≤ 5.15.*
    • unaffected 6.1.165 – ≤ 6.1.*
    • unaffected 6.6.128 – ≤ 6.6.*
    • unaffected 6.12.75 – ≤ 6.12.*
    • unaffected 6.18.16 – ≤ 6.18.*
    • unaffected 6.19.6 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-43124 badge
[![CVE-2026-43124](https://cveledger.app/badge/CVE-2026-43124.svg)](https://cveledger.app/cve/CVE-2026-43124)

Record last updated .