Answer in brief
CVE-2026-43124 records a Unknown severity vulnerability in pstore: ram_core: fix incorrect success return when vmap() fails. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=831b624df1b420c8f9281ed1307a8db23afb72df <d47234840aeb4182ed3ee795c578b1dfa9cbd25b || >=831b624df1b420c8f9281ed1307a8db23afb72df <49918dd52615097529811d21ec6074dd02ebe77c || >=831b624df1b420c8f9281ed1307a8db23afb72df <8baa234181f632cabacf73e4834a910859e9fcc9 || >=831b624df1b420c8f9281ed1307a8db23afb72df <1da904e84de608907662ad8a51ba9c571d61e003 || >=831b624df1b420c8f9281ed1307a8db23afb72df <8d849adfbc3e98417fb541620568db1a759ef441 || >=831b624df1b420c8f9281ed1307a8db23afb72df <2c99326dc1c79b7ce3c8dd92929b5ce724ff70eb || >=831b624df1b420c8f9281ed1307a8db23afb72df <88d5b28f63c7aac1271784e3b800ed405d1cde75 || >=831b624df1b420c8f9281ed1307a8db23afb72df <05363abc7625cf18c96e67f50673cd07f11da5e9 || 9095f19baae92afb978f8df77d19280fe291b337 || 36a9916189b46b78dbf4fa542739b464444f0537 || 1cd01dba1355e291f636555b1920625ed58c1623 || 7026e2457c5b0c0e8a81e65a8209b8420a437b4d || 1e5b387747ba285a64348b9a96b246d0b9d52b03 || d0028f48b33086cf6d8f87831a650866107b5785 || >=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 | d47234840aeb4182ed3ee795c578b1dfa9cbd25b, 49918dd52615097529811d21ec6074dd02ebe77c, 8baa234181f632cabacf73e4834a910859e9fcc9, 1da904e84de608907662ad8a51ba9c571d61e003, 8d849adfbc3e98417fb541620568db1a759ef441, 2c99326dc1c79b7ce3c8dd92929b5ce724ff70eb, 88d5b28f63c7aac1271784e3b800ed405d1cde75, 05363abc7625cf18c96e67f50673cd07f11da5e9, 3.17, 3.19, 4.5, 4.10, 4.15, 4.19 |
| Linux/Linuxgeneric | 4.19 | Not reported |
Published upstream
May 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 6, 2026
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.
Quoted source text, attributed separately from HOL analysis.