Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2026-31399

7.8 · HIGH

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…

Published Apr 3, 2026CWE-416EPSS 0.17%

Overview

CVE-2026-31399 is a high-severity vulnerability. It was published on April 3, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

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

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/2c638259ad750833fd46a0cf57672a618542d84cRefgit.kernel.org/stable/c/6fc36c2a925ceaba203eb13d75a8f0879a2c121bRefgit.kernel.org/stable/c/84af19855d1abdee3c9d57c0684e2868e391793cRefgit.kernel.org/stable/c/9a0fb16ba5b372465a3a1ecd761c6fa911a4ab4dRefgit.kernel.org/stable/c/a226e5b49e5fe8c98b14f8507de670189d191348Refgit.kernel.org/stable/c/a36cf138500e56f50db9f9a33222df6969b38326Refgit.kernel.org/stable/c/a8aec14230322ed8f1e8042b6d656c1631d41163Refgit.kernel.org/stable/c/e48bf8f1d2b12c1c5ba1f609edbd4cde5dadc20e

How CyberStrike helps

Frequently asked questions

What is CVE-2026-31399?

CVE-2026-31399 is a high-severity vulnerability. It was published on April 3, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2026-31399?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-31399?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-31399?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-31399 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999