CVE-2026-31399 — nvdimm/bus: Fix potential use after free in asynchronous initialization
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().
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux, Linux Linux Kernel).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
version e31a8418c8df7e6771414f99ed3d95ba8aca4e05≥ b6eae0f61db27748606cc00dafcfd1e2c032f0a5 and < e48bf8f1d2b12c1c5ba1f609edbd4cde5dadc20e≥ b6eae0f61db27748606cc00dafcfd1e2c032f0a5 and < 2c638259ad750833fd46a0cf57672a618542d84c≥ b6eae0f61db27748606cc00dafcfd1e2c032f0a5 and < a226e5b49e5fe8c98b14f8507de670189d191348≥ b6eae0f61db27748606cc00dafcfd1e2c032f0a5 and < 84af19855d1abdee3c9d57c0684e2868e391793c≥ b6eae0f61db27748606cc00dafcfd1e2c032f0a5 and < a8aec14230322ed8f1e8042b6d656c1631d41163version 8954771abdea5c34280870e35592c7226a816d95version 3e63a7f25cc85d3d3e174b9b0e3489ebb7eaf4ab and 11 moreversion 1490de2bb0836fc0631c04d0559fdf81545b672f≥ b6eae0f61db27748606cc00dafcfd1e2c032f0a5 and < 9a0fb16ba5b372465a3a1ecd761c6fa911a4ab4dversion 4f1a55a4f990016406147cf3e0c9487bf83e50f0≥ 4.4.164 and < 4.5≥ 4.9.137 and < 4.10≥ 4.14.81 and < 4.15≥ 4.18.19 and < 4.19≥ 4.19.2 and < 4.20version 4.20≥ b6eae0f61db27748606cc00dafcfd1e2c032f0a5 and < a36cf138500e56f50db9f9a33222df6969b38326≥ b6eae0f61db27748606cc00dafcfd1e2c032f0a5 and < 6fc36c2a925ceaba203eb13d75a8f0879a2c121b |
Vulnerable | CVE Program (cve.org) e CISA ADP |
| Linux | Linux Kernel |
≥ 4.9.137 and < 4.10≥ 4.4.164 and < 4.5≥ 4.14.81 and < 4.15≥ 4.18.19 and < 4.19≥ 4.19.2 and < 5.10.253≥ 5.11 and < 5.15.203≥ 5.16 and < 6.1.167≥ 6.2 and < 6.6.130 and 7 more≥ 6.7 and < 6.12.78≥ 6.13 and < 6.18.20≥ 6.19 and < 6.19.10version 7.0-rc1version 7.0-rc2version 7.0-rc3version 7.0-rc4 |
Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.8 | CVSS 3.1 | High | 1.8 | 5.9 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.17%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
- Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Record published
- Fix documented
- CVSS changed · 7.8
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
8 on the record
- git.kernel.org/stable/c/a36cf138500e56f50db9f9a33222df6969b38326
- git.kernel.org/stable/c/e48bf8f1d2b12c1c5ba1f609edbd4cde5dadc20e
- git.kernel.org/stable/c/2c638259ad750833fd46a0cf57672a618542d84c
- git.kernel.org/stable/c/a226e5b49e5fe8c98b14f8507de670189d191348
- git.kernel.org/stable/c/a8aec14230322ed8f1e8042b6d656c1631d41163
- git.kernel.org/stable/c/84af19855d1abdee3c9d57c0684e2868e391793c
- git.kernel.org/stable/c/6fc36c2a925ceaba203eb13d75a8f0879a2c121b
- git.kernel.org/stable/c/9a0fb16ba5b372465a3a1ecd761c6fa911a4ab4d
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 7h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 7h
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 1d
- Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 1d
- Unknown CVE-2026-98429 RDMA/efa: Keep EQ resources alive while IRQ is registered 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-31399 is "nvdimm/bus: Fix potential use after free in asynchronous initialization", rated High. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.8 describes technical severity. EPSS 0.17% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.