CVE-2022-48773: xprtrdma: fix pointer derefs in error cases of rpcrdma_ep_create
In the Linux kernel, the following vulnerability has been resolved:
xprtrdma: fix pointer derefs in error cases of rpcrdma_ep_create
If there are failures then we must not leave the non-NULL pointers with
the error value, otherwise `rpcrdma_ep_destroy` gets confused and tries
free them, resulting in an Oops.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel reliability flaw in the xprtrdma component. When endpoint creation fails, bad pointer cleanup can trigger a kernel Oops. Business impact is most likely service disruption on systems using affected kernel builds, but the provided sources do not establish severity, exploitability, or active exploitation.
Executive priority
Treat as a targeted kernel maintenance issue unless your environment relies on xprtrdma/RPC-over-RDMA. No source provided evidence of exploitation, but affected production kernels should be patched through normal vulnerability management.
Technical view
The bug is in rpcrdma_ep_create error handling. Failed setup can leave non-NULL pointers holding error values, causing rpcrdma_ep_destroy to mis-handle cleanup and Oops. The record names Linux kernel as affected and links stable commits resolving the issue.
Likely exposure
Exposure appears limited to Linux systems running affected kernel builds with xprtrdma/RPC-over-RDMA code reachable in their workload. The source bundle lists Linux versions and stable commit references, but exact distro package impact requires vendor kernel mapping.
Exploitation context
The supplied sources do not report active exploitation, public exploit activity, CVSS scoring, or KEV inclusion. The described outcome is a kernel Oops during error cleanup, which points primarily to availability risk.
Researcher notes
Evidence is narrow: the CVE description explains the faulty error-path pointer state and cleanup Oops, but provides no CVSS, CWE, exploit detail, or downstream advisory mapping. Validate branch and distro applicability before assigning operational priority.
Mitigation direction
Update affected Linux kernels to builds containing the linked stable fixes.
Check distribution advisories for exact package versions and backports.
Prioritize systems using xprtrdma or RPC-over-RDMA functionality.
If no vendor advisory exists, follow upstream stable kernel guidance.
Validation and detection
Inventory Linux kernel versions and vendor package releases.
Map installed kernels against the CVE record and linked stable commits.
Identify hosts using xprtrdma or RPC-over-RDMA workloads.
Review system logs for kernel Oops events involving rpcrdma cleanup.
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-48773 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.