# nvdimm/bus: Fix potential use after free in asynchronous initialization

CVE record · `CVE-2026-31399`

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

Published by the CVE Program (CNA: Linux) at 3 Apr 2026, 15:16 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: `b6eae0f61db27748606cc00dafcfd1e2c032f0a5 to before 6fc36c2a925ceaba203eb13d75a8f0879a2c121b` (git)
  - affected: `b6eae0f61db27748606cc00dafcfd1e2c032f0a5 to before a36cf138500e56f50db9f9a33222df6969b38326` (git)
  - affected: `b6eae0f61db27748606cc00dafcfd1e2c032f0a5 to before 9a0fb16ba5b372465a3a1ecd761c6fa911a4ab4d` (git)
  - affected: `b6eae0f61db27748606cc00dafcfd1e2c032f0a5 to before e48bf8f1d2b12c1c5ba1f609edbd4cde5dadc20e` (git)
  - affected: `b6eae0f61db27748606cc00dafcfd1e2c032f0a5 to before 2c638259ad750833fd46a0cf57672a618542d84c` (git)
  - affected: `b6eae0f61db27748606cc00dafcfd1e2c032f0a5 to before a226e5b49e5fe8c98b14f8507de670189d191348` (git)
  - affected: `b6eae0f61db27748606cc00dafcfd1e2c032f0a5 to before 84af19855d1abdee3c9d57c0684e2868e391793c` (git)
  - affected: `b6eae0f61db27748606cc00dafcfd1e2c032f0a5 to before a8aec14230322ed8f1e8042b6d656c1631d41163` (git)
  - affected: `8954771abdea5c34280870e35592c7226a816d95` (git)
  - affected: `3e63a7f25cc85d3d3e174b9b0e3489ebb7eaf4ab` (git)
  - affected: `1490de2bb0836fc0631c04d0559fdf81545b672f` (git)
  - affected: `e31a8418c8df7e6771414f99ed3d95ba8aca4e05` (git)
  - and 6 more
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `4.20`
  - unaffected: `before 4.20` (semver)
  - unaffected: `5.10.253 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.203 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.167 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.130 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.78 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.20 to 6.18.*, inclusive` (semver)
  - unaffected: `6.19.10 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.

> CVE-2026-31399 affects the Linux kernel's nvdimm bus code, specifically asynchronous device initialization, in versions from 4.20 up to the fixes referenced in the CNA's product list. The source gives few details beyond the description of a use-after-free that occurs when device_add() fails in nd_async_device_register(). The affected kernel branches are fixed in the stable releases listed as unaffected (5.10.253, 5.15.203, 6.1.167, 6.6.130 and later point releases), so upgrade to a fixed kernel version for your branch.

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.0012, the 1st percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 3 Apr 2026, 15:16 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-31399)
- 3 Apr 2026, 16:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-31399)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/6fc36c2a925ceaba203eb13d75a8f0879a2c121b>
- <https://git.kernel.org/stable/c/a36cf138500e56f50db9f9a33222df6969b38326>
- <https://git.kernel.org/stable/c/9a0fb16ba5b372465a3a1ecd761c6fa911a4ab4d>
- <https://git.kernel.org/stable/c/e48bf8f1d2b12c1c5ba1f609edbd4cde5dadc20e>
- <https://git.kernel.org/stable/c/2c638259ad750833fd46a0cf57672a618542d84c>
- <https://git.kernel.org/stable/c/a226e5b49e5fe8c98b14f8507de670189d191348>
- <https://git.kernel.org/stable/c/84af19855d1abdee3c9d57c0684e2868e391793c>
- <https://git.kernel.org/stable/c/a8aec14230322ed8f1e8042b6d656c1631d41163>

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-31399>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

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