LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50885: RDMA/rxe: Fix NULL-ptr-deref in rxe_qp_do_cleanup() when socket create failed

In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix NULL-ptr-deref in rxe_qp_do_cleanup() when socket create failed There is a null-ptr-deref when mount.cifs over rdma: BUG: KASAN: null-ptr-deref in rxe_qp_do_cleanup+0x2f3/0x360 [rdma_rxe] Read of size 8 at addr 0000000000000018 by task mount.cifs/3046 CPU: 2 PID: 3046 Comm: mount.cifs Not tainted 6.1.0-rc5+ #62 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-1.fc3 Call Trace: <TASK> dump_stack_lvl+0x34/0x44 kasan_report+0xad/0x130 rxe_qp_do_cleanup+0x2f3/0x360 [rdma_rxe] execute_in_process_context+0x25/0x90 __rxe_cleanup+0x101/0x1d0 [rdma_rxe] rxe_create_qp+0x16a/0x180 [rdma_rxe] create_qp.part.0+0x27d/0x340 ib_create_qp_kernel+0x73/0x160 rdma_create_qp+0x100/0x230 _smbd_get_connection+0x752/0x20f0 smbd_get_connection+0x21/0x40 cifs_get_tcp_session+0x8ef/0xda0 mount_get_conns+0x60/0x750 cifs_mount+0x103/0xd00 cifs_smb3_do_mount+0x1dd/0xcb0 smb3_get_tree+0x1d5/0x300 vfs_get_tree+0x41/0xf0 path_mount+0x9b3/0xdd0 __x64_sys_mount+0x190/0x1d0 do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x46/0xb0 The root cause of the issue is the socket create failed in rxe_qp_init_req(). So move the reset rxe_qp_do_cleanup() after the NULL ptr check.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can crash a system when the software RDMA driver handles a failed socket creation during CIFS over RDMA mounting. The public record does not provide CVSS, confirmed impact beyond a NULL pointer dereference, or evidence of active exploitation.

Executive priority

Treat as a targeted availability risk for Linux hosts using software RDMA and CIFS over RDMA. Patch through normal kernel maintenance, faster for shared or business-critical storage clients. Current public evidence does not justify emergency response absent relevant exposure.

Technical view

In rdma_rxe, rxe_qp_do_cleanup() can dereference NULL after rxe_qp_init_req() fails to create a socket. The trace occurs via mount.cifs using SMB Direct/RDMA. The fix moves cleanup after a NULL pointer check. Linux stable commits are referenced for multiple maintained kernel lines.

Likely exposure

Exposure is most likely on Linux systems using or loading the rdma_rxe software RDMA module with CIFS/SMB over RDMA paths. General Linux servers without RDMA/rxe or CIFS over RDMA usage appear less likely to hit the vulnerable path, based on the provided trace.

Exploitation context

No KEV listing or cited source indicates active exploitation. The documented trigger is mount.cifs over RDMA when socket creation fails. The record supports a kernel NULL pointer dereference; it does not establish remote code execution or privilege escalation.

Researcher notes

The source bundle has no CVSS or CWE and includes ambiguous affected version data. Focus triage on the rdma_rxe cleanup path and vendor backports. Do not assume all Linux deployments are exposed; module availability and CIFS/RDMA usage matter.

Mitigation direction

  • Identify Linux kernels using affected stable lines listed in the CVE record.
  • Apply vendor kernel updates that include the referenced Linux stable fixes.
  • If not needed, disable or avoid rdma_rxe and CIFS over RDMA usage per vendor guidance.
  • Prioritize systems where untrusted users can initiate mounts or RDMA-backed SMB workflows.

Validation and detection

  • Confirm running kernel version against vendor advisories and referenced stable commits.
  • Check whether rdma_rxe is present, loadable, or actively used.
  • Review whether CIFS mounts use RDMA/SMB Direct paths.
  • Search kernel logs for rxe_qp_do_cleanup NULL dereference or related oops traces.
  • Verify the installed kernel contains the applicable stable fix commit.
Prepared
Confidence
medium
Sources
10

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-50885 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
0Timeline events
0ADP providers
9Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux8700e3e7c4857d28ebaa824509934556da0b3e76, 8700e3e7c4857d28ebaa824509934556da0b3e76, 8700e3e7c4857d28ebaa824509934556da0b3e76, 8700e3e7c4857d28ebaa824509934556da0b3e76, 8700e3e7c4857d28ebaa824509934556da0b3e76, 8700e3e7c4857d28ebaa824509934556da0b3e76, 8700e3e7c4857d28ebaa824509934556da0b3e76, 8700e3e7c4857d28ebaa824509934556da0b3e76unaffected
LinuxLinux4.8, 0, 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.