LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50244: cxl: fix possible null-ptr-deref in cxl_pci_init_afu|adapter()

In the Linux kernel, the following vulnerability has been resolved: cxl: fix possible null-ptr-deref in cxl_pci_init_afu|adapter() If device_register() fails in cxl_pci_afu|adapter(), the device is not added, device_unregister() can not be called in the error path, otherwise it will cause a null-ptr-deref because of removing not added device. As comment of device_register() says, it should use put_device() to give up the reference in the error path. So split device_unregister() into device_del() and put_device(), then goes to put dev when register fails.

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 reliability flaw in the CXL PCI driver. If device registration fails during CXL adapter or AFU setup, cleanup can dereference a null pointer and crash kernel code. The source bundle provides no CVSS score, no KEV listing, and no evidence of active exploitation.

Executive priority

Treat this as a targeted Linux kernel maintenance item, not an emergency based on available evidence. Patch through normal kernel update channels, with higher priority for infrastructure using CXL capabilities or custom kernels near the affected versions.

Technical view

The issue is incorrect error-path handling in cxl_pci_afu() and cxl_pci_adapter(). When device_register() fails, device_unregister() is inappropriate because the device was not added. The resolved fix separates removal from reference release by using device_del() and put_device() correctly.

Likely exposure

Exposure appears limited to Linux systems running affected kernel builds where the CXL PCI driver and relevant hardware or initialization path are present. The bundle lists Linux as affected across multiple kernel versions, but does not provide distro package mappings or runtime reachability details.

Exploitation context

No cited source reports exploitation, and KEV is false. The described failure condition is a kernel null-pointer dereference after device_register() failure, suggesting availability impact is the clearest concern. The bundle does not establish remote reachability, privilege requirements, or a practical attack path.

Researcher notes

Evidence is narrow but coherent: the flaw is an error-path null dereference fixed by changing cleanup semantics after device_register() failure. Missing data includes CVSS, CWE, exploitation reports, triggerability, and distro-specific fixed package versions.

Mitigation direction

  • Update to a Linux kernel containing the referenced stable fixes.
  • Use vendor or distribution kernel advisories for package-specific remediation.
  • Prioritize hosts using CXL hardware or loading the CXL PCI driver.
  • If immediate patching is unavailable, review vendor guidance for safe exposure reduction.

Validation and detection

  • Inventory kernel versions across Linux hosts.
  • Identify systems with CXL hardware or CXL PCI driver usage.
  • Compare kernel source or packages against the referenced stable commits.
  • Check distribution advisories for backported fixes.
  • Record systems without CXL reachability as lower validation priority.
Prepared
Confidence
medium
Sources
4

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-2022-50244 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
10Source 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
LinuxLinuxf204e0b8cedd7da1dfcfd05ed6b7692737e24029, f204e0b8cedd7da1dfcfd05ed6b7692737e24029, f204e0b8cedd7da1dfcfd05ed6b7692737e24029, f204e0b8cedd7da1dfcfd05ed6b7692737e24029, f204e0b8cedd7da1dfcfd05ed6b7692737e24029, f204e0b8cedd7da1dfcfd05ed6b7692737e24029, f204e0b8cedd7da1dfcfd05ed6b7692737e24029, f204e0b8cedd7da1dfcfd05ed6b7692737e24029, f204e0b8cedd7da1dfcfd05ed6b7692737e24029unaffected
LinuxLinux3.18, 0, 4.9.337, 4.14.303, 4.19.270, 5.4.229, 5.10.163, 5.15.86, 6.0.16, 6.1.2, 6.2affected
Weakness

CWE details

No CWE listed

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