CVE-2026-31399
What it is
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().
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Weakness
- CWE-416 · Use after free
- Record status
- Analyzed
Affected
- Linux Kernel < 4.5
- Linux Kernel < 4.10
- Linux Kernel < 4.15
- Linux Kernel < 4.19
- Linux Kernel < 5.10.253
- Linux Kernel < 5.15.203
- Linux Kernel < 6.1.167
- Linux Kernel < 6.6.130
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-31399.md and follow it. Check whether this project is affected by CVE-2026-31399. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/2c638259ad750833fd46a0cf57672a618542d84c
- https://git.kernel.org/stable/c/6fc36c2a925ceaba203eb13d75a8f0879a2c121b
- https://git.kernel.org/stable/c/84af19855d1abdee3c9d57c0684e2868e391793c
- https://git.kernel.org/stable/c/9a0fb16ba5b372465a3a1ecd761c6fa911a4ab4d
- https://git.kernel.org/stable/c/a226e5b49e5fe8c98b14f8507de670189d191348
- https://git.kernel.org/stable/c/a36cf138500e56f50db9f9a33222df6969b38326
- https://git.kernel.org/stable/c/a8aec14230322ed8f1e8042b6d656c1631d41163
- https://git.kernel.org/stable/c/e48bf8f1d2b12c1c5ba1f609edbd4cde5dadc20e
References
- https://git.kernel.org/stable/c/2c638259ad750833fd46a0cf57672a618542d84c
- https://git.kernel.org/stable/c/6fc36c2a925ceaba203eb13d75a8f0879a2c121b
- https://git.kernel.org/stable/c/84af19855d1abdee3c9d57c0684e2868e391793c
- https://git.kernel.org/stable/c/9a0fb16ba5b372465a3a1ecd761c6fa911a4ab4d
- https://git.kernel.org/stable/c/a226e5b49e5fe8c98b14f8507de670189d191348
- https://git.kernel.org/stable/c/a36cf138500e56f50db9f9a33222df6969b38326
- https://git.kernel.org/stable/c/a8aec14230322ed8f1e8042b6d656c1631d41163
- https://git.kernel.org/stable/c/e48bf8f1d2b12c1c5ba1f609edbd4cde5dadc20e