CVE-2025-38211

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-07-04. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2025-20045 (ENISA EUVD) · GHSA-wcw7-g3wh-rxf7 (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

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

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
34th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-26). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 4, 2025

Last Modified

August 5, 2026

Advisory Details (10)

Auto-updated Jul 30, 2026
Patch available.
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4328-1] linux-6.1 security update

https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4327-1] linux security update

https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html
Web page

RDMA/iwcm: Fix use-after-free of work objects after cm_id destruction - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fd960b5ddf4faf00da43babdd3acda68842e1f6a
Web page

RDMA/iwcm: Fix use-after-free of work objects after cm_id destruction - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bf7eff5e3a36c54bbe8aff7fd6dd7c07490b81c5
Web page

RDMA/iwcm: Fix use-after-free of work objects after cm_id destruction - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/78381dc8a6b61c9bb9987d37b4d671b99767c4a1
Web page

RDMA/iwcm: Fix use-after-free of work objects after cm_id destruction - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/764c9f69beabef8bdc651a7746c59f7a340d104f
Web page

RDMA/iwcm: Fix use-after-free of work objects after cm_id destruction - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6883b680e703c6b2efddb4e7a8d891ce1803d06b
Web page

RDMA/iwcm: Fix use-after-free of work objects after cm_id destruction - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3b4a50d733acad6831f6bd9288a76a80f70650ac
Web page

RDMA/iwcm: Fix use-after-free of work objects after cm_id destruction - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/23a707bbcbea468eedb398832eeb7e8e0ceafd21
Web page

RDMA/iwcm: Fix use-after-free of work objects after cm_id destruction - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/013dcdf6f03bcedbaf1669e3db71c34a197715b2

Vendor Advisories for CVE-2025-38211(12)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(31)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-ibm-lts-24.04 (6.8.0-1044.44) @ noble2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1023.24) @ noble2026-10-27ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1041.42~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1041.42) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1046.52+fips1) @ noble2026-10-27ubuntu
ubuntulinux-tools-aws-edge (6.14.0-1015.15~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-gcp-edge (6.14.0-1018.19~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-realtime-5.15 (5.15.0.1092.96) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1096.81) @ jammy2026-10-27ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1090.96~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1096.94) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1096.105~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-tools-kvm-5.15 (5.15.0.1088.84) @ jammy2026-10-27ubuntu
ubuntulinux-tools-nvidia-tegra-igx-rt-5.15 (5.15.0.1034.36) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-6.14 (6.14.0-1014.14) @ plucky2026-10-27ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.14.0-1014.14~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1047.50+fips1) @ noble2026-10-27ubuntu
redhatkernel-0:4.18.0-305.179.1.el8_42025-12-04redhat
redhatkernel-0:4.18.0-193.173.1.el8_22025-11-18redhat
redhatkernel-0:4.18.0-372.164.1.el8_62025-10-15redhat
redhatkernel-0:4.18.0-477.114.1.el8_82025-10-08redhat
redhatkernel-rt-0:5.14.0-70.148.1.rt21.220.el9_02025-10-01redhat
redhatkernel-0:5.14.0-70.148.1.el9_02025-10-01redhat
redhatkernel-0:5.14.0-427.91.1.el9_42025-09-25redhat
redhatkernel-0:5.14.0-284.137.1.el9_22025-09-11redhat
redhatkernel-rt-0:5.14.0-284.137.1.rt14.422.el9_22025-09-10redhat
redhatkernel-0:6.12.0-55.30.1.el10_02025-09-02redhat
redhatkernel-0:4.18.0-553.72.1.el8_102025-09-02redhat
redhatkernel-0:5.14.0-570.39.1.el9_62025-09-02redhat
redhatkernel-rt-0:4.18.0-553.72.1.rt7.413.el8_102025-09-02redhat
linuxKernel @ 5.4.296 (fixes >=4.8.0)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (46 versions)
  • every version up to 5.10.244-1: fixed in 5.10.244-1
—
linux-6.16.1.106-3~deb11u1 ... 6.1.148-1~deb11u1 (11 versions)
  • every version up to 6.1.153-1~deb11u1: fixed in 6.1.153-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (41 versions)
  • every version up to 6.1.147-1: fixed in 6.1.147-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.35-1: fixed in 6.12.35-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.35-1: fixed in 6.12.35-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(13)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 42× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 201 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 103 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:42 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  2. 2026-11-01 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  3. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  4. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  5. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  6. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  7. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  8. 2026-10-27 12:46 UTCEG score recompute
  9. 2026-10-27 12:46 UTCVendor advisory
  10. 2026-10-27 12:45 UTCGHSA enrichmentGHSA-wcw7-g3wh-rxf7 · GitHub severity HIGH · GitHub CVSS 7.8
  11. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  12. 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  13. 2026-10-25 16:30 UTCEG score recompute
  14. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  15. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  16. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  17. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  18. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  19. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  20. 2026-10-18 16:59 UTCEG score recompute
  21. 2026-10-18 16:59 UTCVendor advisory
  22. 2026-10-18 16:59 UTCGHSA enrichmentGHSA-wcw7-g3wh-rxf7 · GitHub severity HIGH · GitHub CVSS 7.8
  23. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  24. 2026-10-18 05:36 UTCEG score recompute
  25. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
Show 73 more
  1. 2026-10-16 16:38 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  2. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  3. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  4. 2026-10-13 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  5. 2026-10-12 17:07 UTCEG score recompute
  6. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  7. 2026-10-11 20:40 UTCEG score recompute
  8. 2026-10-11 18:51 UTCEG score recompute
  9. 2026-10-11 15:28 UTCEG score recompute
  10. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  11. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  12. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  13. 2026-10-08 17:09 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  14. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  15. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  16. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  17. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  18. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  19. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  20. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  21. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  22. 2026-09-27 02:15 UTCOSV refresh
  23. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  24. 2026-09-26 00:24 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  25. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  26. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  27. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  28. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  29. 2026-09-17 19:29 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  30. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  31. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  32. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  33. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  34. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  35. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  36. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  37. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  38. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  39. 2026-09-07 11:47 UTCOSV refresh
  40. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  41. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  42. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  43. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  44. 2026-09-01 04:38 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  45. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  46. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  47. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  48. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  49. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  50. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  51. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  52. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  53. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  54. 2026-08-20 21:01 UTCOSV refresh
  55. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  56. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  57. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  58. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  59. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  60. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  61. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  62. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  63. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  64. 2026-08-08 16:36 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  65. 2026-08-07 16:26 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  66. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  67. 2026-08-05 13:06 UTCEG score recompute
  68. 2026-08-05 13:06 UTCVendor advisory
  69. 2026-08-05 13:06 UTCGHSA enrichmentGHSA-wcw7-g3wh-rxf7 · GitHub severity HIGH · GitHub CVSS 7.8
  70. 2026-08-04 15:09 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  71. 2026-08-04 10:37 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  72. 2026-08-03 10:35 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  73. 2026-08-02 02:26 UTCEPSS rescoreEPSS 0.3% · 27th percentile

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-38211?
CVE-2025-38211 is a high-severity vulnerability; its CVE record was published on July 4, 2025. 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…
When was the CVE record for CVE-2025-38211 published?
The CVE record for CVE-2025-38211 was published on July 4, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 5, 2026; the record at its source may have been updated since.
Is CVE-2025-38211 actively exploited?
CVE-2025-38211 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-38211?
CVE-2025-38211 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-38211?
A fix for CVE-2025-38211 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-38211 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-38211

Explore →

Is Your Infrastructure Affected by CVE-2025-38211?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs