LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54323: cxl/pmem: Fix nvdimm registration races

In the Linux kernel, the following vulnerability has been resolved: cxl/pmem: Fix nvdimm registration races A loop of the form: while true; do modprobe cxl_pci; modprobe -r cxl_pci; done ...fails with the following crash signature: BUG: kernel NULL pointer dereference, address: 0000000000000040 [..] RIP: 0010:cxl_internal_send_cmd+0x5/0xb0 [cxl_core] [..] Call Trace: <TASK> cxl_pmem_ctl+0x121/0x240 [cxl_pmem] nvdimm_get_config_data+0xd6/0x1a0 [libnvdimm] nd_label_data_init+0x135/0x7e0 [libnvdimm] nvdimm_probe+0xd6/0x1c0 [libnvdimm] nvdimm_bus_probe+0x7a/0x1e0 [libnvdimm] really_probe+0xde/0x380 __driver_probe_device+0x78/0x170 driver_probe_device+0x1f/0x90 __device_attach_driver+0x85/0x110 bus_for_each_drv+0x7d/0xc0 __device_attach+0xb4/0x1e0 bus_probe_device+0x9f/0xc0 device_add+0x445/0x9c0 nd_async_device_register+0xe/0x40 [libnvdimm] async_run_entry_fn+0x30/0x130 ...namely that the bottom half of async nvdimm device registration runs after the CXL has already torn down the context that cxl_pmem_ctl() needs. Unlike the ACPI NFIT case that benefits from launching multiple nvdimm device registrations in parallel from those listed in the table, CXL is already marked PROBE_PREFER_ASYNCHRONOUS. So provide for a synchronous registration path to preclude this scenario.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel stability flaw in the CXL persistent-memory path. The cited report shows a kernel NULL pointer crash when CXL PCI support is repeatedly loaded and unloaded. Business impact is primarily availability risk on systems using the affected CXL/pmem functionality; public severity and CVSS are not provided.

Executive priority

Treat this as a targeted availability issue, not a confirmed internet-scale emergency. Prioritize validation and patch planning for Linux servers using CXL persistent memory, especially where kernel crashes would affect production availability.

Technical view

The issue is a race in cxl/pmem nvdimm registration. Asynchronous nvdimm registration can continue after CXL teardown removes context required by cxl_pmem_ctl(), causing a NULL pointer dereference. The fix changes CXL registration behavior to use a synchronous path for this case.

Likely exposure

Most relevant to Linux systems using CXL persistent memory or loading the cxl_pci, cxl_pmem, and libnvdimm components. The bundle lists Linux kernel versions including 5.14, 6.1.16, 6.2.3, and 6.3 as affected, but distribution-specific status is not supplied.

Exploitation context

The provided evidence describes a reproducible crash during repeated module load and unload. There is no KEV listing, no cited active exploitation, and no public exploit status in the bundle. Required privileges and remote reachability are not stated.

Researcher notes

The strongest evidence is the kernel commit narrative and crash trace. The record lacks CVSS, CWE, exploitability assessment, and distribution mapping. Avoid broader claims beyond CXL/pmem nvdimm registration race and potential kernel crash.

Mitigation direction

  • Check your Linux vendor advisory for CVE-2023-54323 status.
  • Update to a kernel containing the referenced stable fixes.
  • Prioritize CXL persistent-memory hosts before general Linux fleets.
  • Avoid unnecessary CXL module reload workflows until patched.
  • Track distro backports, since kernel version strings may not show fixes.

Validation and detection

  • Inventory systems with CXL persistent-memory hardware or enabled modules.
  • Check running kernel packages against vendor fixed versions.
  • Confirm whether cxl_pci, cxl_pmem, or libnvdimm are loaded.
  • Review crash logs for matching cxl_pmem_ctl NULL dereference traces.
  • Verify patched systems include the referenced stable commit lineage.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-54323 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux21083f51521fb0f60dbac591f175c3ed48435af4, 21083f51521fb0f60dbac591f175c3ed48435af4, 21083f51521fb0f60dbac591f175c3ed48435af4unaffected
LinuxLinux5.14, 0, 6.1.16, 6.2.3, 6.3affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.