CVE-2026-23348

MEDIUMNVD 4.74.7—
EchelonGraph scoreMEDIUM confidence

Score 4.7 from GitHub Security Advisory published 2026-03-25. NVD baseline CVSS 4.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
4.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.7Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

cxl: Fix race of nvdimm_bus object when creating nvdimm objects

Found issue during running of cxl-translate.sh unit test. Adding a 3s sleep right before the test seems to make the issue reproduce fairly consistently. The cxl_translate module has dependency on cxl_acpi and causes orphaned nvdimm objects to reprobe after cxl_acpi is removed. The nvdimm_bus object is registered by the cxl_nvb object when cxl_acpi_probe() is called. With the nvdimm_bus object missing, __nd_device_register() will trigger NULL pointer dereference when accessing the dev->parent that points to &nvdimm_bus->dev.

[ 192.884510] BUG: kernel NULL pointer dereference, address: 000000000000006c [ 192.895383] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS edk2-20250812-19.fc42 08/12/2025 [ 192.897721] Workqueue: cxl_port cxl_bus_rescan_queue [cxl_core] [ 192.899459] RIP: 0010:kobject_get+0xc/0x90 [ 192.924871] Call Trace: [ 192.925959] [ 192.926976] ? pm_runtime_init+0xb9/0xe0 [ 192.929712] __nd_device_register.part.0+0x4d/0xc0 [libnvdimm] [ 192.933314] __nvdimm_create+0x206/0x290 [libnvdimm] [ 192.936662] cxl_nvdimm_probe+0x119/0x1d0 [cxl_pmem] [ 192.940245] cxl_bus_probe+0x1a/0x60 [cxl_core] [ 192.943349] really_probe+0xde/0x380

This patch also relies on the previous change where devm_cxl_add_nvdimm_bridge() is called from drivers/cxl/pmem.c instead of drivers/cxl/core.c to ensure the dependency of cxl_acpi on cxl_pmem.

  • Set probe_type of cxl_nvb to PROBE_FORCE_SYNCHRONOUS to ensure the
driver is probed synchronously when add_device() is called.
  • Add a check in __devm_cxl_add_nvdimm_bridge() to ensure that the
cxl_nvb driver is attached during cxl_acpi_probe().
  • Take the cxl_root uport_dev lock and the cxl_nvb->dev lock in
devm_cxl_add_nvdimm() before checking nvdimm_bus is valid.
  • Set cxl_nvdimm flag to CXL_NVD_F_INVALIDATED so cxl_nvdimm_probe()
will exit with -EBUSY.

The removal of cxl_nvdimm devices should prevent any orphaned devices from probing once the nvdimm_bus is gone.

[ dj: Fixed 0-day reported kdoc issue. ] [ dj: Fix cxl_nvb reference leak on error. Gregory (kreview-0811365) ]

CVSS v3
4.7
EG Score
4.7(medium)
EG Risk
26(Track)
EG Risk 26/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
Severity47% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
0%
KEV
Not listed

Published

March 25, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Aug 9, 2026
No patch confirmed yet.
generic

cxl: Fix race of nvdimm_bus object when creating nvdimm objects - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/96a1fd0d84b17360840f344826897fa71049870e
generic

cxl: Fix race of nvdimm_bus object when creating nvdimm objects - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5fc4e150c5ada5f7d20d8f9f1b351f10481fbdf7
generic

cxl: Fix race of nvdimm_bus object when creating nvdimm objects - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5b230daeee420833287cc77314439903e5312f10

Vendor Advisories for CVE-2026-23348(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.18.17—osv

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (174 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (120 versions)6.19.8-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 4× in last 7d / 19× 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 159 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-23348?
CVE-2026-23348 is a medium vulnerability published on March 25, 2026. In the Linux kernel, the following vulnerability has been resolved: cxl: Fix race of nvdimm_bus object when creating nvdimm objects Found issue during running of cxl-translate.sh unit test. Adding a 3s sleep right before the test seems to make the issue reproduce fairly consistently. The…
When was CVE-2026-23348 disclosed?
CVE-2026-23348 was first published in the National Vulnerability Database on March 25, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23348 actively exploited?
CVE-2026-23348 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 99.5% of all scored CVEs.
What is the CVSS score of CVE-2026-23348?
CVE-2026-23348 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2026-23348?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23348, 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-23348

Explore →

Is Your Infrastructure Affected by CVE-2026-23348?

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

Start Free Scan →Browse All CVEs