CVE-2026-31399 json
nvdimm/bus: Fix potential use after free in asynchronous initialization
published 2026-04-03 7 mo ago modified 2026-11-05 3 d ago also EUVD-2026-18780
- cvss
- 7.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 1%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
nvdimm/bus: Fix potential use after free in asynchronous initialization
Dingisoul with KASAN reports a use after free if device_add() fails in nd_async_device_register().
Commit b6eae0f61db2 ("libnvdimm: Hold reference on parent while scheduling async init") correctly added a reference on the parent device to be held until asynchronous initialization was complete. However, if device_add() results in an allocation failure the ref count of the device drops to 0 prior to the parent pointer being accessed. Thus resulting in use after free.
The bug bot AI correctly identified the fix. Save a reference to the parent pointer to be used to drop the parent reference regardless of the outcome of device_add().
Patch / fix
- Linux Linux 4.5, 4.10, 4.15, 4.19, 4.20, 5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.78, 6.18.20, 6.19.10, 7.0
- linux Debian 12 6.1.170-1
- linux Debian 13 6.12.85-1
- linux Debian 14 6.19.10-1
debian advisories DEBIAN-CVE-2026-31399
- linux Ubuntu 22.04 LTS 5.15.0-186.196
- linux Ubuntu 24.04 LTS 6.8.0-136.136
- linux-aws Ubuntu 22.04 LTS 5.15.0-1112.119
- linux-aws Ubuntu 24.04 LTS 6.8.0-1061.64
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1112.122
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1064.72
- linux-gke Ubuntu 22.04 LTS 5.15.0-1108.114
- linux-gke Ubuntu 24.04 LTS 6.8.0-1059.67
ubuntu advisories UBUNTU-CVE-2026-31399
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/6fc36c2a925ceaba203eb13d75a8f0879a2c121b commit
- git.kernel.org/stable/c/a36cf138500e56f50db9f9a33222df6969b38326 commit
- git.kernel.org/stable/c/9a0fb16ba5b372465a3a1ecd761c6fa911a4ab4d commit
- git.kernel.org/stable/c/e48bf8f1d2b12c1c5ba1f609edbd4cde5dadc20e commit
- git.kernel.org/stable/c/2c638259ad750833fd46a0cf57672a618542d84c commit
- git.kernel.org/stable/c/a226e5b49e5fe8c98b14f8507de670189d191348 commit
- git.kernel.org/stable/c/84af19855d1abdee3c9d57c0684e2868e391793c commit
- git.kernel.org/stable/c/a8aec14230322ed8f1e8042b6d656c1631d41163 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-31399 updated cvss 4.7
kernel: nvdimm/bus: Fix potential use after free in asynchronous initialization
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelaffected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3 d ago
Exploit prediction
0.12% chance of exploitation in the next 30 days, higher than 1% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-416 Use After Free
- Technology feeds
References
-
git.kernel.org
/stable/c/6fc36c2a925ceaba203eb13d75a8f0879a2c121b
patch
-
git.kernel.org
/stable/c/a36cf138500e56f50db9f9a33222df6969b38326
patch
-
git.kernel.org
/stable/c/9a0fb16ba5b372465a3a1ecd761c6fa911a4ab4d
patch
-
git.kernel.org
/stable/c/e48bf8f1d2b12c1c5ba1f609edbd4cde5dadc20e
patch
-
git.kernel.org
/stable/c/2c638259ad750833fd46a0cf57672a618542d84c
patch
-
git.kernel.org
/stable/c/a226e5b49e5fe8c98b14f8507de670189d191348
patch
-
git.kernel.org
/stable/c/84af19855d1abdee3c9d57c0684e2868e391793c
patch
-
git.kernel.org
/stable/c/a8aec14230322ed8f1e8042b6d656c1631d41163
patch
Sources
- CVE List CVE-2026-31399
- NVD CVE-2026-31399
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.