Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-31399

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

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

Timeline

  1. ID reserved

    By Linux

  2. · 25 days later

    Published

  3. · 7 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-31399, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.12% · top 98% of all CVEs (12 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected b6eae0f61db27748606cc00dafcfd1e2c032f0a5 – < 6fc36c2a925ceaba203eb13d75a8f0879a2c121b
    • affected b6eae0f61db27748606cc00dafcfd1e2c032f0a5 – < a36cf138500e56f50db9f9a33222df6969b38326
    • affected b6eae0f61db27748606cc00dafcfd1e2c032f0a5 – < 9a0fb16ba5b372465a3a1ecd761c6fa911a4ab4d
    • affected b6eae0f61db27748606cc00dafcfd1e2c032f0a5 – < e48bf8f1d2b12c1c5ba1f609edbd4cde5dadc20e
    • affected b6eae0f61db27748606cc00dafcfd1e2c032f0a5 – < 2c638259ad750833fd46a0cf57672a618542d84c
    • affected b6eae0f61db27748606cc00dafcfd1e2c032f0a5 – < a226e5b49e5fe8c98b14f8507de670189d191348
    • affected b6eae0f61db27748606cc00dafcfd1e2c032f0a5 – < 84af19855d1abdee3c9d57c0684e2868e391793c
    • affected b6eae0f61db27748606cc00dafcfd1e2c032f0a5 – < a8aec14230322ed8f1e8042b6d656c1631d41163
    • affected 8954771abdea5c34280870e35592c7226a816d95
    • affected 3e63a7f25cc85d3d3e174b9b0e3489ebb7eaf4ab
    • affected 1490de2bb0836fc0631c04d0559fdf81545b672f
    • affected e31a8418c8df7e6771414f99ed3d95ba8aca4e05
    • affected 4f1a55a4f990016406147cf3e0c9487bf83e50f0
    • affected 4.4.164 – < 4.5
    • affected 4.9.137 – < 4.10
    • affected 4.14.81 – < 4.15
    • affected 4.18.19 – < 4.19
    • affected 4.19.2 – < 4.20
  • Linux · Linux

    • affected 4.20
    • unaffected < 4.20
    • unaffected 5.10.253 – ≤ 5.10.*
    • unaffected 5.15.203 – ≤ 5.15.*
    • unaffected 6.1.167 – ≤ 6.1.*
    • unaffected 6.6.130 – ≤ 6.6.*
    • unaffected 6.12.78 – ≤ 6.12.*
    • unaffected 6.18.20 – ≤ 6.18.*
    • unaffected 6.19.10 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-31399 badge
[![CVE-2026-31399](https://cveledger.app/badge/CVE-2026-31399.svg)](https://cveledger.app/cve/CVE-2026-31399)

Record last updated .