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

CVE record · `CVE-2026-43124`

- **Identifiers:** `CVE-2026-43124`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 6 May 2026
- **Updated:** 6 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 6 May 2026, 11:27 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `831b624df1b420c8f9281ed1307a8db23afb72df to before d47234840aeb4182ed3ee795c578b1dfa9cbd25b` (git)
  - affected: `831b624df1b420c8f9281ed1307a8db23afb72df to before 49918dd52615097529811d21ec6074dd02ebe77c` (git)
  - affected: `831b624df1b420c8f9281ed1307a8db23afb72df to before 8baa234181f632cabacf73e4834a910859e9fcc9` (git)
  - affected: `831b624df1b420c8f9281ed1307a8db23afb72df to before 1da904e84de608907662ad8a51ba9c571d61e003` (git)
  - affected: `831b624df1b420c8f9281ed1307a8db23afb72df to before 8d849adfbc3e98417fb541620568db1a759ef441` (git)
  - affected: `831b624df1b420c8f9281ed1307a8db23afb72df to before 2c99326dc1c79b7ce3c8dd92929b5ce724ff70eb` (git)
  - affected: `831b624df1b420c8f9281ed1307a8db23afb72df to before 88d5b28f63c7aac1271784e3b800ed405d1cde75` (git)
  - affected: `831b624df1b420c8f9281ed1307a8db23afb72df to before 05363abc7625cf18c96e67f50673cd07f11da5e9` (git)
  - affected: `9095f19baae92afb978f8df77d19280fe291b337` (git)
  - affected: `36a9916189b46b78dbf4fa542739b464444f0537` (git)
  - affected: `1cd01dba1355e291f636555b1920625ed58c1623` (git)
  - affected: `7026e2457c5b0c0e8a81e65a8209b8420a437b4d` (git)
  - and 8 more
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `4.19`
  - unaffected: `before 4.19` (semver)
  - unaffected: `5.10.252 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.202 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.165 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.128 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.75 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.16 to 6.18.*, inclusive` (semver)
  - unaffected: `6.19.6 to 6.19.*, inclusive` (semver)
  - unaffected: `7.0 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Linux kernel pstore (ram_core) reports success when vmap() fails at a nonzero offset, so later buffer access can dereference an invalid address and crash. The source gives few details on what triggers this or who can reach it. Upgrade to 5.10.252, 5.15.202, 6.1.165, 6.6.128 or a later release in those series.

Written 17 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0013, the 2nd percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 6 May 2026, 11:27 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-43124)
- 6 May 2026, 12:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-43124)

## Sources

- [CVE List: CVE-2026-43124](https://www.cve.org/CVERecord?id=CVE-2026-43124)
- [NVD: CVE-2026-43124](https://nvd.nist.gov/vuln/detail/CVE-2026-43124)

### References from the CNA

- <https://git.kernel.org/stable/c/d47234840aeb4182ed3ee795c578b1dfa9cbd25b>
- <https://git.kernel.org/stable/c/49918dd52615097529811d21ec6074dd02ebe77c>
- <https://git.kernel.org/stable/c/8baa234181f632cabacf73e4834a910859e9fcc9>
- <https://git.kernel.org/stable/c/1da904e84de608907662ad8a51ba9c571d61e003>
- <https://git.kernel.org/stable/c/8d849adfbc3e98417fb541620568db1a759ef441>
- <https://git.kernel.org/stable/c/2c99326dc1c79b7ce3c8dd92929b5ce724ff70eb>
- <https://git.kernel.org/stable/c/88d5b28f63c7aac1271784e3b800ed405d1cde75>
- <https://git.kernel.org/stable/c/05363abc7625cf18c96e67f50673cd07f11da5e9>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-43124>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-43124/>. Everything for agents: <https://agentprime.io/llms.txt>.
