VulnerabilityPublished 3 Apr 2026Updated 5 Nov 2026

CVE-2026-31399: Linux kernel · nvdimm/bus: Fix potential use after free in asynchronous initialization

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in e48bf8f1d2b12c1c5ba1f609edbd4cde5dadc20e : update Linux kernel when convenient.

Data as of 5 Nov 2026, 21:49 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch

Available – fixed in e48bf8f1d2b12c1c5ba1f609edbd4cde5dadc20e, a226e5b49e5fe8c98b14f8507de670189d191348, a36cf138500e56f50db9f9a33222df6969b38326 +10

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected >=4.4.164 <4.5 >=4.9.137 <4.10 >=4.14.81 <4.15 >=4.18.19 <4.19 >=4.19.2 <4.20	Fixed in e48bf8f1d2b12c1c5ba1f609edbd4cde5dadc20e a226e5b49e5fe8c98b14f8507de670189d191348 a36cf138500e56f50db9f9a33222df6969b38326 a8aec14230322ed8f1e8042b6d656c1631d41163 84af19855d1abdee3c9d57c0684e2868e391793c 9a0fb16ba5b372465a3a1ecd761c6fa911a4ab4d 6fc36c2a925ceaba203eb13d75a8f0879a2c121b 4.20 4.19 4.15 4.10 4.5 2c638259ad750833fd46a0cf57672a618542d84c
LinuxLinux	Affected =4.20	Fixed in–

Description

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().

References

Community reviews

Loading reviews…