CVE-2026-31399

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-04-03. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

April 3, 2026

Last Modified

July 24, 2026

Advisory Details (8)

Auto-updated May 20, 2026
No patch confirmed yet.
generic

nvdimm/bus: Fix potential use after free in asynchronous initialization - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e48bf8f1d2b12c1c5ba1f609edbd4cde5dadc20e
generic

nvdimm/bus: Fix potential use after free in asynchronous initialization - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a8aec14230322ed8f1e8042b6d656c1631d41163
generic

nvdimm/bus: Fix potential use after free in asynchronous initialization - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a36cf138500e56f50db9f9a33222df6969b38326
generic

nvdimm/bus: Fix potential use after free in asynchronous initialization - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a226e5b49e5fe8c98b14f8507de670189d191348
generic

nvdimm/bus: Fix potential use after free in asynchronous initialization - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9a0fb16ba5b372465a3a1ecd761c6fa911a4ab4d
generic

nvdimm/bus: Fix potential use after free in asynchronous initialization - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/84af19855d1abdee3c9d57c0684e2868e391793c
generic

nvdimm/bus: Fix potential use after free in asynchronous initialization - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6fc36c2a925ceaba203eb13d75a8f0879a2c121b
generic

nvdimm/bus: Fix potential use after free in asynchronous initialization - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2c638259ad750833fd46a0cf57672a618542d84c

Vendor Advisories for CVE-2026-31399(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(17)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)5.10.257-1
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)6.1.170-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (119 versions)6.19.10-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(23)

Data Freshness Timeline

(refreshed 7× in last 7d / 57× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 193 total refreshes for this CVE.

  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-02 14:11 UTCEPSS rescore
  3. 2026-09-02 11:14 UTCOSV refresh
  4. 2026-09-01 13:53 UTCEPSS rescore
  5. 2026-09-01 04:39 UTCEPSS rescore
  6. 2026-09-01 04:39 UTCEPSS rescore
  7. 2026-08-30 19:17 UTCEPSS rescore
  8. 2026-08-28 21:41 UTCEPSS rescore
  9. 2026-08-27 14:25 UTCEPSS rescore
  10. 2026-08-26 14:46 UTCEPSS rescore
  11. 2026-08-24 14:17 UTCEPSS rescore
  12. 2026-08-21 23:49 UTCEPSS rescore
  13. 2026-08-20 22:55 UTCEPSS rescore
  14. 2026-08-20 22:55 UTCEPSS rescore
  15. 2026-08-19 17:03 UTCEPSS rescore
  16. 2026-08-18 13:48 UTCEPSS rescore
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 09:16 UTCEG score recompute
  19. 2026-08-16 09:16 UTCVendor advisory
  20. 2026-08-16 09:16 UTCGHSA enrichment
  21. 2026-08-16 02:14 UTCEPSS rescore
  22. 2026-08-15 01:30 UTCEPSS rescore
  23. 2026-08-14 18:51 UTCVendor advisory
  24. 2026-08-14 18:51 UTCGHSA enrichment
  25. 2026-08-14 05:42 UTCEG score recompute
Show 75 more
  1. 2026-08-14 05:42 UTCVendor advisory
  2. 2026-08-14 05:42 UTCGHSA enrichment
  3. 2026-08-13 22:00 UTCEPSS rescore
  4. 2026-08-13 09:55 UTCVendor advisory
  5. 2026-08-13 09:55 UTCGHSA enrichment
  6. 2026-08-12 19:58 UTCEG score recompute
  7. 2026-08-12 19:58 UTCVendor advisory
  8. 2026-08-12 19:58 UTCGHSA enrichment
  9. 2026-08-12 13:50 UTCEPSS rescore
  10. 2026-08-11 20:17 UTCVendor advisory
  11. 2026-08-11 20:17 UTCGHSA enrichment
  12. 2026-08-11 03:26 UTCEG score recompute
  13. 2026-08-11 03:26 UTCVendor advisory
  14. 2026-08-11 03:26 UTCGHSA enrichment
  15. 2026-08-11 00:00 UTCEPSS rescore
  16. 2026-08-10 04:40 UTCVendor advisory
  17. 2026-08-10 04:40 UTCGHSA enrichment
  18. 2026-08-09 16:56 UTCVendor advisory
  19. 2026-08-09 16:56 UTCGHSA enrichment
  20. 2026-08-09 05:13 UTCEG score recompute
  21. 2026-08-09 05:13 UTCVendor advisory
  22. 2026-08-09 05:13 UTCGHSA enrichment
  23. 2026-08-08 16:37 UTCEPSS rescore
  24. 2026-08-08 03:02 UTCEG score recompute
  25. 2026-08-08 03:02 UTCVendor advisory
  26. 2026-08-08 03:02 UTCGHSA enrichment
  27. 2026-08-07 15:20 UTCEG score recompute
  28. 2026-08-07 15:20 UTCVendor advisory
  29. 2026-08-07 15:20 UTCGHSA enrichment
  30. 2026-08-06 13:46 UTCEPSS rescore
  31. 2026-08-06 13:15 UTCVendor advisory
  32. 2026-08-06 13:15 UTCGHSA enrichment
  33. 2026-08-06 00:19 UTCEG score recompute
  34. 2026-08-06 00:19 UTCVendor advisory
  35. 2026-08-06 00:19 UTCGHSA enrichment
  36. 2026-08-05 19:17 UTCEPSS rescore
  37. 2026-08-04 15:10 UTCEPSS rescore
  38. 2026-08-03 22:38 UTCEG score recompute
  39. 2026-08-03 22:38 UTCVendor advisory
  40. 2026-08-03 22:38 UTCGHSA enrichment
  41. 2026-08-03 10:36 UTCEPSS rescore
  42. 2026-08-03 02:19 UTCVendor advisory
  43. 2026-08-03 02:19 UTCGHSA enrichment
  44. 2026-08-02 14:34 UTCEG score recompute
  45. 2026-08-02 14:34 UTCVendor advisory
  46. 2026-08-02 14:34 UTCGHSA enrichment
  47. 2026-08-02 02:27 UTCEPSS rescore
  48. 2026-08-01 04:16 UTCEPSS rescore
  49. 2026-07-30 16:27 UTCEPSS rescore
  50. 2026-07-30 01:30 UTCEPSS rescore
  51. 2026-07-28 15:36 UTCEPSS rescore
  52. 2026-07-26 14:54 UTCEPSS rescore
  53. 2026-07-26 14:54 UTCEPSS rescore
  54. 2026-07-26 09:17 UTCEG score recompute
  55. 2026-07-26 09:17 UTCVendor advisory
  56. 2026-07-26 09:17 UTCGHSA enrichment
  57. 2026-07-25 14:18 UTCEPSS rescore
  58. 2026-07-25 14:17 UTCEPSS rescore
  59. 2026-07-24 14:17 UTCEPSS rescore
  60. 2026-07-23 14:18 UTCEPSS rescore
  61. 2026-07-23 14:18 UTCEPSS rescore
  62. 2026-07-23 03:08 UTCEG score recompute
  63. 2026-07-22 14:08 UTCEPSS rescore
  64. 2026-07-22 14:08 UTCEPSS rescore
  65. 2026-07-21 15:24 UTCEPSS rescore
  66. 2026-07-21 15:24 UTCEPSS rescore
  67. 2026-07-20 17:08 UTCEPSS rescore
  68. 2026-07-20 17:08 UTCEPSS rescore
  69. 2026-07-19 14:31 UTCEPSS rescore
  70. 2026-07-19 14:31 UTCEPSS rescore
  71. 2026-07-18 10:04 UTCEPSS rescore
  72. 2026-07-18 10:04 UTCEPSS rescore
  73. 2026-07-17 03:24 UTCOSV refresh
  74. 2026-07-16 17:03 UTCEPSS rescore
  75. 2026-07-16 17:03 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-31399?
CVE-2026-31399 is a high vulnerability published on April 3, 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 ndasyncdevice_register(). Commit b6eae0f61db2 ("libnvdimm: Hold reference on parent…
When was CVE-2026-31399 disclosed?
CVE-2026-31399 was first published in the National Vulnerability Database on April 3, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31399 actively exploited?
CVE-2026-31399 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.0% of all scored CVEs.
What is the CVSS score of CVE-2026-31399?
CVE-2026-31399 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-31399?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31399, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-31399

Explore →

Is Your Infrastructure Affected by CVE-2026-31399?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.