CVE-2023-53525

RDMA/cma: Allow UD qp_type to join multicast only

MEDIUM

5.5

CVSS Score

Published: October 1, 2025 at 11:46 AM UTC

Updated: June 17, 2026 at 06:45 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.1%

Description

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/[email protected]/

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

v ≥ 5.8.17v ≥ 5.9.25.10 ≤ v < 5.10.1785.10 ≤ v < 5.15.1085.10 ≤ v < 6.1.255.10 ≤ v < 6.2.125.10 ≤ v < 6.35.11 ≤ v < 5.15.1085.16 ≤ v < 6.1.255.8.17 ≤ v < 5.95.9.2 ≤ v < 5.105.9.2 ≤ v < 5.10.1786.2 ≤ v < 6.2.125.10 5.8.17 5.9.2 6.3 rc1 6.3 rc2 6.3 rc3 6.3 rc4 6.3 rc5 6.3 rc6b5de0c60cc30c2a3513c7188c73f3f29acc29234b8d1adbff983be0b54f61c9a4169609d7fab0620feed39c8d1282279fcb30612aa0e8d2635c11280

Vendor states this is fixed in 02eabb635bc64bd1e3a7cf887d6d182bffb64b99 (fixed)

Vendor states this is fixed in 48e8e7851dc0b1584d83817a78fc7108c8904b54 (fixed)

Vendor states this is fixed in 58e84f6b3e84e46524b7e5a916b53c1ad798bc8f (fixed)

Vendor states this is fixed in ae11498851423d6de27aebfe12a5ee85060ab1d5 (fixed)

Vendor states this is fixed in bb18b9dbac2bbdf7695e0bfaac4bf944ff7b207d (fixed)

Vendor states this is fixed in 5.10 (unaffected)

Vendor states this is fixed in 5.10.178 (unaffected)

Vendor states this is fixed in 5.15.108 (unaffected)

Affected range stops below 5.9, so it looks safe — our inference, not a vendor statement

Vendor states this is fixed in 6.1.25 (unaffected)

Vendor states this is fixed in 6.2.12 (unaffected)

Vendor states this is fixed in 6.3 (unaffected)