CVE-2024-47696

RDMA/iwcm: Fix WARNING:at_kernel/workqueue.c:#check_flush_dependency

HIGH

7.8

CVSS Score

Published: October 21, 2024 at 11:53 AM UTC

Updated: October 15, 2026 at 01:18 AM UTC

12 products affected across 2 vendorsLinux KernelSIMATIC S7-1500 TM MFPRUGGEDCOM RST2428P Firmware

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

HIGH7.8

Exploit prediction

EPSS 0.7%

SSVC

No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: RDMA/iwcm: Fix WARNING:at_kernel/workqueue.c:#check_flush_dependency In the commit aee2424246f9 ("RDMA/iwcm: Fix a use-after-free related to destroying CM IDs"), the function flush_workqueue is invoked to flush the work queue iwcm_wq. But at that time, the work queue iwcm_wq was created via the function alloc_ordered_workqueue without the flag WQ_MEM_RECLAIM. Because the current process is trying to flush the whole iwcm_wq, if iwcm_wq doesn't have the flag WQ_MEM_RECLAIM, verify that the current process is not reclaiming memory or running on a workqueue which doesn't have the flag WQ_MEM_RECLAIM as that can break forward-progress guarantee leading to a deadlock. The call trace is as below: [ 125.350876][ T1430] Call Trace: [ 125.356281][ T1430] <TASK> [ 125.361285][ T1430] ? __warn (kernel/panic.c:693) [ 125.367640][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.375689][ T1430] ? report_bug (lib/bug.c:180 lib/bug.c:219) [ 125.382505][ T1430] ? handle_bug (arch/x86/kernel/traps.c:239) [ 125.388987][ T1430] ? exc_invalid_op (arch/x86/kernel/traps.c:260 (discriminator 1)) [ 125.395831][ T1430] ? asm_exc_invalid_op (arch/x86/include/asm/idtentry.h:621) [ 125.403125][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.410984][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.418764][ T1430] __flush_workqueue (kernel/workqueue.c:3970) [ 125.426021][ T1430] ? __pfx___might_resched (kernel/sched/core.c:10151) [ 125.433431][ T1430] ? destroy_cm_id (drivers/infiniband/core/iwcm.c:375) iw_cm [ 125.441209][ T1430] ? __pfx___flush_workqueue (kernel/workqueue.c:3910) [ 125.473900][ T1430] ? _raw_spin_lock_irqsave (arch/x86/include/asm/atomic.h:107 include/linux/atomic/atomic-arch-fallback.h:2170 include/linux/atomic/atomic-instrumented.h:1302 include/asm-generic/qspinlock.h:111 include/linux/spinlock.h:187 include/linux/spinlock_api_smp.h:111 kernel/locking/spinlock.c:162) [ 125.473909][ T1430] ? __pfx__raw_spin_lock_irqsave (kernel/locking/spinlock.c:161) [ 125.482537][ T1430] _destroy_id (drivers/infiniband/core/cma.c:2044) rdma_cm [ 125.495072][ T1430] nvme_rdma_free_queue (drivers/nvme/host/rdma.c:656 drivers/nvme/host/rdma.c:650) nvme_rdma [ 125.505827][ T1430] nvme_rdma_reset_ctrl_work (drivers/nvme/host/rdma.c:2180) nvme_rdma [ 125.505831][ T1430] process_one_work (kernel/workqueue.c:3231) [ 125.515122][ T1430] worker_thread (kernel/workqueue.c:3306 kernel/workqueue.c:3393) [ 125.515127][ T1430] ? __pfx_worker_thread (kernel/workqueue.c:3339) [ 125.531837][ T1430] kthread (kernel/kthread.c:389) [ 125.539864][ T1430] ? __pfx_kthread (kernel/kthread.c:342) [ 125.550628][ T1430] ret_from_fork (arch/x86/kernel/process.c:147) [ 125.558840][ T1430] ? __pfx_kthread (kernel/kthread.c:342) [ 125.558844][ T1430] ret_from_fork_asm (arch/x86/entry/entry_64.S:257) [ 125.566487][ T1430] </TASK> [ 125.566488][ T1430] ---[ end trace 0000000000000000 ]---

Affected

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

Linux Kernel · Linux

95%

4.19.320 ≤ v < 5.45.10.224 ≤ v < 5.10.2275.15.165 ≤ v < 5.15.1685.4.282 ≤ v < 5.106.1.103 ≤ v < 6.1.1136.10.3 ≤ v < 6.10.136.11 ≤ v < 6.11.26.6.44 ≤ v < 6.6.544.19.320 5.10.224 5.15.165 5.4.282557d035fe88d78dd51664f4dc0e1896c04c97cf66.1.103 6.10.3 6.11 6.6.447f25f296fc9bd0435be14e89bf657cd615a2357494ee7ff99b87435ec63211f632918dc7f44dac79aee2424246f9f1dadc33faa78990c1e2eb7826e4d91d253c87fd1efece521ff2612078a35af673c6dc8074b8901caabb97c2d353abd6b4e7fa5a59a5ee39384ee787e86e9db4efb843818ef0ea9cb8aeff5bbbdee08287d75d72e65b72a2b76d9637892a

Vendor states this is fixed in 29b3bbd912b8db86df7a3c180b910ccb621f5635 (fixed)

Vendor states this is fixed in 2efe8da2ddbf873385b4bc55366d09350b408df6 (fixed)

Vendor states this is fixed in 86dfdd8288907f03c18b7fb462e0e232c4f98d89 (fixed)

Vendor states this is fixed in 8b7df76356d098f85f3bd2c7cf6fb43f531893d7 (fixed)

Vendor states this is fixed in a09dc967b3c58899e259c0aea092f421d22a0b04 (fixed)

Vendor states this is fixed in a64f30db12bdc937c5108158d98c8eab1925c548 (fixed)

Vendor states this is fixed in c8b18a75282cfd27822a8cc3c1f005c1ac8d1a58 (fixed)

Vendor states this is fixed in da0392698c62397c19deb1b9e9bdf2fbb5a9420e (fixed)

Vendor states this is fixed in da2708a19f45b4a7278adf523837c8db21d1e2b5 (fixed)

Vendor states this is fixed in 4.19.323 (unaffected)

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

Vendor states this is fixed in 5.10.227 (unaffected)

Vendor states this is fixed in 5.15.168 (unaffected)

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

Vendor states this is fixed in 5.4.285 (unaffected)

Vendor states this is fixed in 6.1.113 (unaffected)

Vendor states this is fixed in 6.10.13 (unaffected)

Vendor states this is fixed in 6.11 (unaffected)

Vendor states this is fixed in 6.11.2 (unaffected)

Vendor states this is fixed in 6.12 (unaffected)

Vendor states this is fixed in 6.6.54 (unaffected)

RUGGEDCOM RST2428P Firmware · Siemens

60%

v < V3.2