Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-38211: RDMA/iwcm: Fix use-after-free of work objects after cm_id destruction

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.40% (FIRST EPSS).
  • 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 013dcdf6f03bcedbaf1669e3db71c34a197715b2, 23a707bbcbea468eedb398832eeb7e8e0ceafd21, 3b4a50d733acad6831f6bd9288a76a80f70650ac; azl3 kernel 6.6.92.2-2 on Azure Linux 3.0 6.6.96.1-1.
  • Severity is disputed: the assigning authority (CNA) scores it 9.8, NVD 7.8.

Low priority for now. Upgrade to Linux Linux 013dcdf6f03bcedbaf1669e3db71c34a197715b2, 23a707bbcbea468eedb398832eeb7e8e0ceafd21, 3b4a50d733acad6831f6bd9288a76a80f70650ac; azl3 kernel 6.6.92.2-2 on Azure Linux 3.0 6.6.96.1-1 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 use-after-free of work objects after cm_id destruction The commit 59c68ac31e15 ("iw_cm: free cm_id resources on the last deref") simplified cm_id resource management by freeing cm_id once all references to the cm_id were removed. The references are removed either upon completion of iw_cm event handlers or when the application destroys the cm_id. This commit introduced the use-after-free condition where cm_id_private object could still be in use by event handler works during the destruction of cm_id. The commit aee2424246f9 ("RDMA/iwcm: Fix a use-after-free related to destroying CM IDs") addressed this use-after- free by flushing all pending works at the cm_id destruction. However, still another use-after-free possibility remained. It happens with the work objects allocated for each cm_id_priv within alloc_work_entries() during cm_id creation, and subsequently freed in dealloc_work_entries() once all references to the cm_id are removed. If the cm_id's last reference is decremented in the event handler work, the work object for the work itself gets removed, and causes the use- after-free BUG below: BUG: KASAN: slab-use-after-free in __pwq_activate_work+0x1ff/0x250 Read of size 8 at addr ffff88811f9cf800 by task kworker/u16:1/147091 CPU: 2 UID: 0 PID: 147091 Comm: kworker/u16:1 Not tainted 6.15.0-rc2+ #27 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-3.fc41 04/01/2014 Workqueue: 0x0 (iw_cm_wq) Call Trace: <TASK> dump_stack_lvl+0x6a/0x90 print_report+0x174/0x554 ? __virt_addr_valid+0x208/0x430 ? __pwq_activate_work+0x1ff/0x250 kasan_report+0xae/0x170 ? __pwq_activate_work+0x1ff/0x250 __pwq_activate_work+0x1ff/0x250 pwq_dec_nr_in_flight+0x8c5/0xfb0 process_one_work+0xc11/0x1460 ? __pfx_process_one_work+0x10/0x10 ? assign_work+0x16c/0x240 worker_thread+0x5ef/0xfd0 ? __pfx_worker_thread+0x10/0x10 kthread+0x3b0/0x770 ? __pfx_kthread+0x10/0x10 ? rcu_is_watching+0x11/0xb0 ? _raw_spin_unlock_irq+0x24/0x50 ? rcu_is_watching+0x11/0xb0 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x30/0x70 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> Allocated by task 147416: kasan_save_stack+0x2c/0x50 kasan_save_track+0x10/0x30 __kasan_kmalloc+0xa6/0xb0 alloc_work_entries+0xa9/0x260 [iw_cm] iw_cm_connect+0x23/0x4a0 [iw_cm] rdma_connect_locked+0xbfd/0x1920 [rdma_cm] nvme_rdma_cm_handler+0x8e5/0x1b60 [nvme_rdma] cma_cm_event_handler+0xae/0x320 [rdma_cm] cma_work_handler+0x106/0x1b0 [rdma_cm] process_one_work+0x84f/0x1460 worker_thread+0x5ef/0xfd0 kthread+0x3b0/0x770 ret_from_fork+0x30/0x70 ret_from_fork_asm+0x1a/0x30 Freed by task 147091: kasan_save_stack+0x2c/0x50 kasan_save_track+0x10/0x30 kasan_save_free_info+0x37/0x60 __kasan_slab_free+0x4b/0x70 kfree+0x13a/0x4b0 dealloc_work_entries+0x125/0x1f0 [iw_cm] iwcm_deref_id+0x6f/0xa0 [iw_cm] cm_work_handler+0x136/0x1ba0 [iw_cm] process_one_work+0x84f/0x1460 worker_thread+0x5ef/0xfd0 kthread+0x3b0/0x770 ret_from_fork+0x30/0x70 ret_from_fork_asm+0x1a/0x30 Last potentially related work creation: kasan_save_stack+0x2c/0x50 kasan_record_aux_stack+0xa3/0xb0 __queue_work+0x2ff/0x1390 queue_work_on+0x67/0xc0 cm_event_handler+0x46a/0x820 [iw_cm] siw_cm_upcall+0x330/0x650 [siw] siw_cm_work_handler+0x6b9/0x2b20 [siw] process_one_work+0x84f/0x1460 worker_thread+0x5ef/0xfd0 kthread+0x3b0/0x770 ret_from_fork+0x30/0x70 ret_from_fork_asm+0x1a/0x30 This BUG is reproducible by repeating the blktests test case nvme/061 for the rdma transport and the siw driver. To avoid the use-after-free of cm_id_private work objects, ensure that the last reference to the cm_id is decremented not in the event handler works, but in the cm_id destruction context. For that purpose, mo ---truncated---

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Jul 4, 2025
Updated
Aug 5, 2026
EPSS
0.4% · 34th 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.4%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.8
CNA · Linux
9.8
2.0 point gap

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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-2025-38211

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.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

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
debiandebian linux

Affected versions

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

  • debian debian linux11.0
  • linux linux kernel5.5 and later · before 5.10.240
  • linux linux kernel5.11 and later · before 5.15.186
  • linux linux kernel5.16 and later · before 6.1.142
  • linux linux kernel4.8 and later · before 5.4.296
  • linux linux kernel6.7 and later · before 6.12.35
  • linux linux kernel6.13 and later · before 6.15.4
  • linux linux kernel6.2 and later · before 6.6.95

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

    • 4.8affected
    • 59c68ac31e15ad09d2cb04734e3c8c544a95f8d4 and later · before 013dcdf6f03bcedbaf1669e3db71c34a197715b2affected · git
    • 59c68ac31e15ad09d2cb04734e3c8c544a95f8d4 and later · before bf7eff5e3a36c54bbe8aff7fd6dd7c07490b81c5affected · git
    • 59c68ac31e15ad09d2cb04734e3c8c544a95f8d4 and later · before 3b4a50d733acad6831f6bd9288a76a80f70650acaffected · git
    • 59c68ac31e15ad09d2cb04734e3c8c544a95f8d4 and later · before 78381dc8a6b61c9bb9987d37b4d671b99767c4a1affected · git
    • 59c68ac31e15ad09d2cb04734e3c8c544a95f8d4 and later · before 23a707bbcbea468eedb398832eeb7e8e0ceafd21affected · git
    • 59c68ac31e15ad09d2cb04734e3c8c544a95f8d4 and later · before 764c9f69beabef8bdc651a7746c59f7a340d104faffected · git
    • 59c68ac31e15ad09d2cb04734e3c8c544a95f8d4 and later · before fd960b5ddf4faf00da43babdd3acda68842e1f6aaffected · git
    • 59c68ac31e15ad09d2cb04734e3c8c544a95f8d4 and later · before 6883b680e703c6b2efddb4e7a8d891ce1803d06baffected · git
    • before 4.8not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-55.30.1.el10_06.12.0-55.30.1.el10_0
AlmaLinux:10kernel-docbefore 6.12.0-55.30.1.el10_06.12.0-55.30.1.el10_0
AlmaLinux:8bpftoolbefore 4.18.0-553.72.1.el8_104.18.0-553.72.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.72.1.el8_104.18.0-553.72.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.72.1.el8_104.18.0-553.72.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.72.1.el8_104.18.0-553.72.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.72.1.el8_104.18.0-553.72.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.72.1.el8_104.18.0-553.72.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.72.1.el8_104.18.0-553.72.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.72.1.el8_104.18.0-553.72.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.72.1.el8_104.18.0-553.72.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.72.1.el8_104.18.0-553.72.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.72.1.el8_104.18.0-553.72.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.72.1.el8_104.18.0-553.72.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.72.1.el8_104.18.0-553.72.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.72.1.el8_104.18.0-553.72.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.72.1.el8_104.18.0-553.72.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.72.1.rt7.413.el8_104.18.0-553.72.1.rt7.413.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.72.1.rt7.413.el8_104.18.0-553.72.1.rt7.413.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.72.1.rt7.413.el8_104.18.0-553.72.1.rt7.413.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.72.1.rt7.413.el8_104.18.0-553.72.1.rt7.413.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.72.1.rt7.413.el8_104.18.0-553.72.1.rt7.413.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.72.1.rt7.413.el8_104.18.0-553.72.1.rt7.413.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.72.1.rt7.413.el8_104.18.0-553.72.1.rt7.413.el8_10

+96

Same product

linux: all records

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-2025-38208Jul 4, 2025 · smb: client: add NULL check in automount_fullpath
    22Monitor
  • ← EarlierCVE-2025-38210Jul 4, 2025 · configfs-tsm-report: Fix NULL dereference of tsm_ops
    22Monitor
  • Later →CVE-2025-38214Jul 4, 2025 · fbdev: Fix fb_set_var to prevent null-ptr-deref in fb_videomode_to_var
    22Monitor

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 Linux013dcdf6f03bcedbaf1669e3db71c34a197715b2Vendor (CNA)
Linux Linux23a707bbcbea468eedb398832eeb7e8e0ceafd21Vendor (CNA)
Linux Linux3b4a50d733acad6831f6bd9288a76a80f70650acVendor (CNA)
Linux Linux6883b680e703c6b2efddb4e7a8d891ce1803d06bVendor (CNA)
Linux Linux764c9f69beabef8bdc651a7746c59f7a340d104fVendor (CNA)
Linux Linux78381dc8a6b61c9bb9987d37b4d671b99767c4a1Vendor (CNA)
Linux Linuxbf7eff5e3a36c54bbe8aff7fd6dd7c07490b81c5Vendor (CNA)
Linux Linuxfd960b5ddf4faf00da43babdd3acda68842e1f6aVendor (CNA)
azl3 kernel 6.6.92.2-2 on Azure Linux 3.06.6.96.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:bpftool4.18.0-553.72.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.72.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-abi-stablelists6.12.0-55.30.1.el10_0 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-core4.18.0-553.72.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-cross-headers4.18.0-553.72.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug4.18.0-553.72.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-core4.18.0-553.72.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-devel4.18.0-553.72.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules4.18.0-553.72.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules-extra4.18.0-553.72.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-devel4.18.0-553.72.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-doc6.12.0-55.30.1.el10_0 · AlmaLinux:10Package registry (OSV)
debian:linux6.1.147-1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-55.30.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-55.30.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-55.30.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-55.30.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-55.30.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-55.30.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-55.30.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-debug-devel0:6.12.0-55.30.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)

+6

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.

Credits

All researchers

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.

The bug in code

The whole CWE-416 class

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

Show all references (9 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records