Skip to content
Noroxi
CVE-2026-31399· NVD / CVE Program· CNA Linux

nvdimm/bus: Fix potential use after free in asynchronous initialization

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 2c638259ad750833fd46a0cf57672a618542d84c, 4.10, 4.15.

Low priority for now. Upgrade to Linux Linux 2c638259ad750833fd46a0cf57672a618542d84c, 4.10, 4.15 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Apr 3, 2026
Updated
Jul 24, 2026
EPSS
0.1% · 6th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-31399

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel4.4.164 and later · before 4.5
  • linux linux kernel4.9.137 and later · before 4.10
  • linux linux kernel4.14.81 and later · before 4.15
  • linux linux kernel4.18.19 and later · before 4.19
  • linux linux kernel4.19.2 and later · before 5.10.253
  • linux linux kernel5.11 and later · before 5.15.203
  • linux linux kernel5.16 and later · before 6.1.167
  • linux linux kernel6.2 and later · before 6.6.130
  • linux linux kernel6.7 and later · before 6.12.78
  • linux linux kernel6.13 and later · before 6.18.20
  • linux linux kernel6.19 and later · before 6.19.10
  • linux linux kernel7.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 8954771abdea5c34280870e35592c7226a816d95, 3e63a7f25cc85d3d3e174b9b0e3489ebb7eaf4ab, 1490de2bb0836fc0631c04d0559fdf81545b672f, e31a8418c8df7e6771414f99ed3d95ba8aca4e05, 4f1a55a4f990016406147cf3e0c9487bf83e50f0, 4.20affected
    • b6eae0f61db27748606cc00dafcfd1e2c032f0a5 and later · before 6fc36c2a925ceaba203eb13d75a8f0879a2c121baffected · git
    • b6eae0f61db27748606cc00dafcfd1e2c032f0a5 and later · before a36cf138500e56f50db9f9a33222df6969b38326affected · git
    • b6eae0f61db27748606cc00dafcfd1e2c032f0a5 and later · before 9a0fb16ba5b372465a3a1ecd761c6fa911a4ab4daffected · git
    • b6eae0f61db27748606cc00dafcfd1e2c032f0a5 and later · before e48bf8f1d2b12c1c5ba1f609edbd4cde5dadc20eaffected · git
    • b6eae0f61db27748606cc00dafcfd1e2c032f0a5 and later · before 2c638259ad750833fd46a0cf57672a618542d84caffected · git
    • b6eae0f61db27748606cc00dafcfd1e2c032f0a5 and later · before a226e5b49e5fe8c98b14f8507de670189d191348affected · git
    • b6eae0f61db27748606cc00dafcfd1e2c032f0a5 and later · before 84af19855d1abdee3c9d57c0684e2868e391793caffected · git
    • b6eae0f61db27748606cc00dafcfd1e2c032f0a5 and later · before a8aec14230322ed8f1e8042b6d656c1631d41163affected · git
    • 4.4.164 and later · before 4.5affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.170-16.1.170-1
Debian:13linuxbefore 6.12.85-16.12.85-1
Debian:14linuxbefore 6.19.10-16.19.10-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now
  • CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
    83Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-31397Apr 3, 2026 · mm/huge_memory: fix use of NULL folio in move_pages_huge_pmd()
    31Monitor
  • ← EarlierCVE-2026-31398Apr 3, 2026 · mm/rmap: fix incorrect pte restoration for lazyfree folios
    31Monitor
  • Later →CVE-2026-31400Apr 3, 2026 · sunrpc: fix cache_request leak in cache_release
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux2c638259ad750833fd46a0cf57672a618542d84cVendor (CNA)
Linux Linux4.10Vendor (CNA)
Linux Linux4.15Vendor (CNA)
Linux Linux4.19Vendor (CNA)
Linux Linux4.20Vendor (CNA)
Linux Linux4.5Vendor (CNA)
Linux Linux6fc36c2a925ceaba203eb13d75a8f0879a2c121bVendor (CNA)
Linux Linux84af19855d1abdee3c9d57c0684e2868e391793cVendor (CNA)
Linux Linux9a0fb16ba5b372465a3a1ecd761c6fa911a4ab4dVendor (CNA)
Linux Linuxa226e5b49e5fe8c98b14f8507de670189d191348Vendor (CNA)
Linux Linuxa36cf138500e56f50db9f9a33222df6969b38326Vendor (CNA)
Linux Linuxa8aec14230322ed8f1e8042b6d656c1631d41163Vendor (CNA)
Linux Linuxe48bf8f1d2b12c1c5ba1f609edbd4cde5dadc20eVendor (CNA)
debian:linux6.1.170-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records