CVE-2023-53525: RDMA/cma: Allow UD qp_type to join multicast only
In the Linux kernel, the following vulnerability has been resolved:
RDMA/cma: Allow UD qp_type to join multicast only
As for multicast:
- The SIDR is the only mode that makes sense;
- Besides PS_UDP, other port spaces like PS_IB is also allowed, as it is
UD compatible. In this case qkey also needs to be set [1].
This patch allows only UD qp_type to join multicast, and set qkey to
default if it's not set, to fix an uninit-value error: the ib->rec.qkey
field is accessed without being initialized.
=====================================================
BUG: KMSAN: uninit-value in cma_set_qkey drivers/infiniband/core/cma.c:510 [inline]
BUG: KMSAN: uninit-value in cma_make_mc_event+0xb73/0xe00 drivers/infiniband/core/cma.c:4570
cma_set_qkey drivers/infiniband/core/cma.c:510 [inline]
cma_make_mc_event+0xb73/0xe00 drivers/infiniband/core/cma.c:4570
cma_iboe_join_multicast drivers/infiniband/core/cma.c:4782 [inline]
rdma_join_multicast+0x2b83/0x30a0 drivers/infiniband/core/cma.c:4814
ucma_process_join+0xa76/0xf60 drivers/infiniband/core/ucma.c:1479
ucma_join_multicast+0x1e3/0x250 drivers/infiniband/core/ucma.c:1546
ucma_write+0x639/0x6d0 drivers/infiniband/core/ucma.c:1732
vfs_write+0x8ce/0x2030 fs/read_write.c:588
ksys_write+0x28c/0x520 fs/read_write.c:643
__do_sys_write fs/read_write.c:655 [inline]
__se_sys_write fs/read_write.c:652 [inline]
__ia32_sys_write+0xdb/0x120 fs/read_write.c:652
do_syscall_32_irqs_on arch/x86/entry/common.c:114 [inline]
__do_fast_syscall_32+0x96/0xf0 arch/x86/entry/common.c:180
do_fast_syscall_32+0x34/0x70 arch/x86/entry/common.c:205
do_SYSENTER_32+0x1b/0x20 arch/x86/entry/common.c:248
entry_SYSENTER_compat_after_hwframe+0x4d/0x5c
Local variable ib.i created at:
cma_iboe_join_multicast drivers/infiniband/core/cma.c:4737 [inline]
rdma_join_multicast+0x586/0x30a0 drivers/infiniband/core/cma.c:4814
ucma_process_join+0xa76/0xf60 drivers/infiniband/core/ucma.c:1479
CPU: 0 PID: 29874 Comm: syz-executor.3 Not tainted 5.16.0-rc3-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
=====================================================
[1] https://lore.kernel.org/linux-rdma/20220117183832.GD84788@nvidia.com/
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel RDMA multicast handling flaw. A local path in the RDMA connection manager could use an uninitialized qkey value. The public record shows a kernel fix, but no CVSS score or confirmed active exploitation.
Executive priority
Treat as a targeted kernel maintenance issue, not an internet-wide emergency. Prioritize RDMA-capable infrastructure and shared compute systems where local users or workloads can reach kernel RDMA interfaces.
Technical view
The issue is in drivers/infiniband/core/cma.c. Non-UD queue pair types could reach multicast join handling where ib->rec.qkey was accessed before initialization. The fix restricts multicast joins to UD qp_type and assigns a default qkey when absent.
Likely exposure
Exposure is most likely on Linux systems running affected kernels with RDMA/InfiniBand/RDMA CM functionality enabled or accessible. Evidence points to a local userspace RDMA CM path through ucma_write/sys_write, not a demonstrated remote network exploit.
Exploitation context
The bundle cites a KMSAN uninitialized-value report from syzkaller on Linux 5.16.0-rc3. KEV is false, and the provided sources do not claim exploitation in the wild or provide a working exploit.
Researcher notes
The source evidence is limited to the CVE text and kernel stable commits. The reported failure mode is uninitialized memory use in multicast event creation, with the remediation constraining allowed qp_type and qkey initialization.
Mitigation direction
Apply Linux kernel updates that include the referenced stable fixes.
Use distribution vendor advisories to map fixed kernel package versions.
Inventory hosts with RDMA, InfiniBand, or RDMA CM enabled.
Where patching is delayed, reduce RDMA userspace access if vendor-supported.
Monitor CVE and vendor guidance because no CVSS score is provided.
Validation and detection
Check running kernel versions against affected and fixed vendor ranges.
Confirm patched kernels include one relevant stable commit from the CVE references.
Identify systems exposing RDMA userspace CM functionality.
Review logs or crash reports for RDMA cma or ucma kernel faults.
Prioritize validation on compute, HPC, storage, or low-latency networking hosts.
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-53525 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
6Source 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:46 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.