Answer in brief
CVE-2026-31399 records a Unknown severity vulnerability in nvdimm/bus: Fix potential use after free in asynchronous initialization. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=b6eae0f61db27748606cc00dafcfd1e2c032f0a5 <6fc36c2a925ceaba203eb13d75a8f0879a2c121b || >=b6eae0f61db27748606cc00dafcfd1e2c032f0a5 <a36cf138500e56f50db9f9a33222df6969b38326 || >=b6eae0f61db27748606cc00dafcfd1e2c032f0a5 <9a0fb16ba5b372465a3a1ecd761c6fa911a4ab4d || >=b6eae0f61db27748606cc00dafcfd1e2c032f0a5 <e48bf8f1d2b12c1c5ba1f609edbd4cde5dadc20e || >=b6eae0f61db27748606cc00dafcfd1e2c032f0a5 <2c638259ad750833fd46a0cf57672a618542d84c || >=b6eae0f61db27748606cc00dafcfd1e2c032f0a5 <a226e5b49e5fe8c98b14f8507de670189d191348 || >=b6eae0f61db27748606cc00dafcfd1e2c032f0a5 <84af19855d1abdee3c9d57c0684e2868e391793c || >=b6eae0f61db27748606cc00dafcfd1e2c032f0a5 <a8aec14230322ed8f1e8042b6d656c1631d41163 || 8954771abdea5c34280870e35592c7226a816d95 || 3e63a7f25cc85d3d3e174b9b0e3489ebb7eaf4ab || 1490de2bb0836fc0631c04d0559fdf81545b672f || e31a8418c8df7e6771414f99ed3d95ba8aca4e05 || 4f1a55a4f990016406147cf3e0c9487bf83e50f0 || >=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 | 6fc36c2a925ceaba203eb13d75a8f0879a2c121b, a36cf138500e56f50db9f9a33222df6969b38326, 9a0fb16ba5b372465a3a1ecd761c6fa911a4ab4d, e48bf8f1d2b12c1c5ba1f609edbd4cde5dadc20e, 2c638259ad750833fd46a0cf57672a618542d84c, a226e5b49e5fe8c98b14f8507de670189d191348, 84af19855d1abdee3c9d57c0684e2868e391793c, a8aec14230322ed8f1e8042b6d656c1631d41163, 4.5, 4.10, 4.15, 4.19, 4.20 |
| Linux/Linuxgeneric | 4.20 | Not reported |
Published upstream
Apr 3, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 5, 2026
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().
Quoted source text, attributed separately from HOL analysis.