CVE-2023-54323: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-9rp2-rcxm-vpww
Share
Published
Advisory Summary

CVE-2023-54323 is a security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2023-54323 at a Glance

CVE Identifier CVE-2023-54323
GHSA Identifier GHSA-9rp2-rcxm-vpww
Severity N/A
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2023-54323

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2023-54323, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

References

NVD — CVE-2023-54323 NVD
https://nvd.nist.gov/vuln/detail/CVE-2023-54323
git.kernel.org/stable/c/18c65667fa... WEB
https://git.kernel.org/stable/c/18c65667fa9104780eeaa0dc1bc240f0c2094772
git.kernel.org/stable/c/a371788d4f... WEB
https://git.kernel.org/stable/c/a371788d4f4a7f59eecd22644331d599979fd283
git.kernel.org/stable/c/f57aec443c... WEB
https://git.kernel.org/stable/c/f57aec443c24d2e8e1f3b5b4856aea12ddda4254

Frequently Asked Questions

What is CVE-2023-54323?
CVE-2023-54323 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2023-54323?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2023-54323?
CVE-2023-54323 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2023-54323?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-9rp2-rcxm-vpww",
  "modified" : "2025-12-30T15:30:36Z",
  "published" : "2025-12-30T15:30:36Z",
  "aliases" : [ "CVE-2023-54323" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ncxl/pmem: Fix nvdimm registration races\n\nA loop of the form:\n\n    while true; do modprobe cxl_pci; modprobe -r cxl_pci; done\n\n...fails with the following crash signature:\n\n    BUG: kernel NULL pointer dereference, address: 0000000000000040\n    [..]\n    RIP: 0010:cxl_internal_send_cmd+0x5/0xb0 [cxl_core]\n    [..]\n    Call Trace:\n     <TASK>\n     cxl_pmem_ctl+0x121/0x240 [cxl_pmem]\n     nvdimm_get_config_data+0xd6/0x1a0 [libnvdimm]\n     nd_label_data_init+0x135/0x7e0 [libnvdimm]\n     nvdimm_probe+0xd6/0x1c0 [libnvdimm]\n     nvdimm_bus_probe+0x7a/0x1e0 [libnvdimm]\n     really_probe+0xde/0x380\n     __driver_probe_device+0x78/0x170\n     driver_probe_device+0x1f/0x90\n     __device_attach_driver+0x85/0x110\n     bus_for_each_drv+0x7d/0xc0\n     __device_attach+0xb4/0x1e0\n     bus_probe_device+0x9f/0xc0\n     device_add+0x445/0x9c0\n     nd_async_device_register+0xe/0x40 [libnvdimm]\n     async_run_entry_fn+0x30/0x130\n\n...namely that the bottom half of async nvdimm device registration runs\nafter the CXL has already torn down the context that cxl_pmem_ctl()\nneeds. Unlike the ACPI NFIT case that benefits from launching multiple\nnvdimm device registrations in parallel from those listed in the table,\nCXL is already marked PROBE_PREFER_ASYNCHRONOUS. So provide for a\nsynchronous registration path to preclude this scenario.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2023-54323"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/18c65667fa9104780eeaa0dc1bc240f0c2094772"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a371788d4f4a7f59eecd22644331d599979fd283"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f57aec443c24d2e8e1f3b5b4856aea12ddda4254"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2025-12-30T13:16:21Z"
  }
}