CVE-2026-43124
pstore: ram_core: fix incorrect success return when vmap() fails
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.17, 3.19, 4.5, 4.10, 4.15, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 3.16.62 · fixed in 3.17; From 3.18.123 · fixed in 3.19; From 4.4.158 · fixed in 4.5; From 4.9.129 · fixed in 4.10; From 4.14.72 · fixed in 4.15; From 4.18.10 · fixed in 4.19
- Linux Linux
4.19
References 8
git.kernel.org
- stable/c/d47234840aeb4182ed3ee795c578b1dfa9cbd25b
- stable/c/49918dd52615097529811d21ec6074dd02ebe77c
- stable/c/8baa234181f632cabacf73e4834a910859e9fcc9
- stable/c/1da904e84de608907662ad8a51ba9c571d61e003
- stable/c/8d849adfbc3e98417fb541620568db1a759ef441
- stable/c/2c99326dc1c79b7ce3c8dd92929b5ce724ff70eb
- stable/c/88d5b28f63c7aac1271784e3b800ed405d1cde75
- stable/c/05363abc7625cf18c96e67f50673cd07f11da5e9