Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-47696: RDMA/iwcm: Fix WARNING:at_kernel/workqueue.c:#check_flush_dependency

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.72% (FIRST EPSS); higher than 54.1% of all records.
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 29b3bbd912b8db86df7a3c180b910ccb621f5635, 2efe8da2ddbf873385b4bc55366d09350b408df6, 4.19.323; Azure Linux 3.0 ARM 6.6.56.1-5; Azure Linux 3.0 x64 6.6.56.1-5.

Low priority for now. Upgrade to Linux Linux 29b3bbd912b8db86df7a3c180b910ccb621f5635, 2efe8da2ddbf873385b4bc55366d09350b408df6, 4.19.323; Azure Linux 3.0 ARM 6.6.56.1-5; Azure Linux 3.0 x64 6.6.56.1-5 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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 ]---

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Oct 21, 2024
Updated
Oct 15, 2026
EPSS
0.7% · 54th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.7%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.8
CNA · Linux
7.5
0.3 point gap

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-47696

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel4.19.320 and later · before 5.4
  • linux linux kernel5.4.282 and later · before 5.10
  • linux linux kernel5.10.224 and later · before 5.10.227
  • linux linux kernel5.15.165 and later · before 5.15.168
  • linux linux kernel6.1.103 and later · before 6.1.113
  • linux linux kernel6.6.44 and later · before 6.6.54
  • linux linux kernel6.10.3 and later · before 6.10.13
  • linux linux kernel6.11 and later · before 6.11.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.11affected
    • d91d253c87fd1efece521ff2612078a35af673c6 and later · before da2708a19f45b4a7278adf523837c8db21d1e2b5affected · git
    • 7f25f296fc9bd0435be14e89bf657cd615a23574 and later · before 29b3bbd912b8db86df7a3c180b910ccb621f5635affected · git
    • 94ee7ff99b87435ec63211f632918dc7f44dac79 and later · before 2efe8da2ddbf873385b4bc55366d09350b408df6affected · git
    • 557d035fe88d78dd51664f4dc0e1896c04c97cf6 and later · before da0392698c62397c19deb1b9e9bdf2fbb5a9420eaffected · git
    • dc8074b8901caabb97c2d353abd6b4e7fa5a59a5 and later · before a64f30db12bdc937c5108158d98c8eab1925c548affected · git
    • ff5bbbdee08287d75d72e65b72a2b76d9637892a and later · before 8b7df76356d098f85f3bd2c7cf6fb43f531893d7affected · git
    • ee39384ee787e86e9db4efb843818ef0ea9cb8ae and later · before c8b18a75282cfd27822a8cc3c1f005c1ac8d1a58affected · git
    • aee2424246f9f1dadc33faa78990c1e2eb7826e4 and later · before a09dc967b3c58899e259c0aea092f421d22a0b04affected · git
    • aee2424246f9f1dadc33faa78990c1e2eb7826e4 and later · before 86dfdd8288907f03c18b7fb462e0e232c4f98d89affected · git

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.115-16.1.115-1
Debian:13linuxbefore 6.11.2-16.11.2-1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-47685Oct 21, 2024 · netfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put()
    36Monitor
  • ← EarlierCVE-2024-47692Oct 21, 2024 · nfsd: return -EINVAL when namelen is 0
    26Monitor
  • Later →CVE-2024-47697Oct 21, 2024 · drivers: media: dvb-frontends/rtl2830: fix an out-of-bounds write error
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux29b3bbd912b8db86df7a3c180b910ccb621f5635Vendor (CNA)
Linux Linux2efe8da2ddbf873385b4bc55366d09350b408df6Vendor (CNA)
Linux Linux4.19.323Vendor (CNA)
Linux Linux5.10.227Vendor (CNA)
Linux Linux5.15.168Vendor (CNA)
Linux Linux5.4.285Vendor (CNA)
Linux Linux6.1.113Vendor (CNA)
Linux Linux6.10.13Vendor (CNA)
Linux Linux6.6.54Vendor (CNA)
Linux Linux86dfdd8288907f03c18b7fb462e0e232c4f98d89Vendor (CNA)
Linux Linux8b7df76356d098f85f3bd2c7cf6fb43f531893d7Vendor (CNA)
Linux Linuxa09dc967b3c58899e259c0aea092f421d22a0b04Vendor (CNA)
Linux Linuxa64f30db12bdc937c5108158d98c8eab1925c548Vendor (CNA)
Linux Linuxc8b18a75282cfd27822a8cc3c1f005c1ac8d1a58Vendor (CNA)
Linux Linuxda0392698c62397c19deb1b9e9bdf2fbb5a9420eVendor (CNA)
Linux Linuxda2708a19f45b4a7278adf523837c8db21d1e2b5Vendor (CNA)
Azure Linux 3.0 ARM6.6.56.1-5 · kernelMicrosoft (MSRC)
Azure Linux 3.0 x646.6.56.1-5 · kernelMicrosoft (MSRC)
debian:linux6.1.115-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records