CVE-2023-53479: cxl/acpi: Fix a use-after-free in cxl_parse_cfmws()
In the Linux kernel, the following vulnerability has been resolved:
cxl/acpi: Fix a use-after-free in cxl_parse_cfmws()
KASAN and KFENCE detected an user-after-free in the CXL driver. This
happens in the cxl_decoder_add() fail path. KASAN prints the following
error:
BUG: KASAN: slab-use-after-free in cxl_parse_cfmws (drivers/cxl/acpi.c:299)
This happens in cxl_parse_cfmws(), where put_device() is called,
releasing cxld, which is accessed later.
Use the local variables in the dev_err() instead of pointing to the
released memory. Since the dev_err() is printing a resource, change the open
coded print format to use the %pr format specifier.
Security readout for executives and security teams
Plain-English summary
CVE-2023-53479 is a Linux kernel bug in the CXL ACPI driver. A failure path can access memory after it has been released, which kernel debugging tools detected. Public sources do not provide CVSS scoring or active exploitation evidence.
Executive priority
Treat as a normal-priority kernel maintenance item unless CXL-enabled infrastructure is business-critical. There is no public evidence of exploitation, but kernel memory-safety bugs should not remain unpatched long-term.
Technical view
The issue is a use-after-free in cxl_parse_cfmws() during the cxl_decoder_add() failure path. put_device() can release cxld, but later error logging still references released memory. The fix changes logging to use local variables and the %pr resource format.
Likely exposure
Exposure appears limited to Linux systems running affected kernel versions with the CXL ACPI driver path present or enabled. Organizations should map this against kernels listed in the CVE record and their distribution backports.
Exploitation context
No KEV listing or cited source indicates active exploitation. The public description shows detection by KASAN and KFENCE, suggesting a memory-safety defect found through kernel testing rather than documented in-the-wild abuse.
Researcher notes
The record lacks CVSS, CWE, and exploitability detail. The vulnerability is specifically tied to error handling and logging after put_device(). Validate fixes by code review or distro patch metadata rather than relying only on upstream version numbers.
Mitigation direction
Check vendor or Linux distribution advisories for fixed kernel packages.
Update to a kernel containing the referenced stable fixes.
Prioritize systems using CXL-capable hardware or CXL ACPI support.
If updates are delayed, follow vendor guidance for risk reduction.
Validation and detection
Inventory running Linux kernel versions across affected systems.
Check whether CXL ACPI support is enabled or relevant to the hardware.
Verify the installed kernel includes one of the referenced stable commits or a backport.
Review vendor advisories for exact fixed package versions.
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-53479 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Oct 1, 2025, 11:42 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.