CVE-2025-38161

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Score 5.5 from GitHub Security Advisory published 2025-07-03. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2025-19783 (ENISA EUVD) · GHSA-hc4c-5v7j-vr7h (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

RDMA/mlx5: Fix error flow upon firmware failure for RQ destruction

Upon RQ destruction if the firmware command fails which is the last resource to be destroyed some SW resources were already cleaned regardless of the failure.

Now properly rollback the object to its original state upon such failure.

In order to avoid a use-after free in case someone tries to destroy the object again, which results in the following kernel trace: refcount_t: underflow; use-after-free. WARNING: CPU: 0 PID: 37589 at lib/refcount.c:28 refcount_warn_saturate+0xf4/0x148 Modules linked in: rdma_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_umad(OE) mlx5_ib(OE) rfkill mlx5_core(OE) mlxdevm(OE) ib_uverbs(OE) ib_core(OE) psample mlxfw(OE) mlx_compat(OE) macsec tls pci_hyperv_intf sunrpc vfat fat virtio_net net_failover failover fuse loop nfnetlink vsock_loopback vmw_vsock_virtio_transport_common vmw_vsock_vmci_transport vmw_vmci vsock xfs crct10dif_ce ghash_ce sha2_ce sha256_arm64 sha1_ce virtio_console virtio_gpu virtio_blk virtio_dma_buf virtio_mmio dm_mirror dm_region_hash dm_log dm_mod xpmem(OE) CPU: 0 UID: 0 PID: 37589 Comm: python3 Kdump: loaded Tainted: G OE ------- --- 6.12.0-54.el10.aarch64 #1 Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : refcount_warn_saturate+0xf4/0x148 lr : refcount_warn_saturate+0xf4/0x148 sp : ffff80008b81b7e0 x29: ffff80008b81b7e0 x28: ffff000133d51600 x27: 0000000000000001 x26: 0000000000000000 x25: 00000000ffffffea x24: ffff00010ae80f00 x23: ffff00010ae80f80 x22: ffff0000c66e5d08 x21: 0000000000000000 x20: ffff0000c66e0000 x19: ffff00010ae80340 x18: 0000000000000006 x17: 0000000000000000 x16: 0000000000000020 x15: ffff80008b81b37f x14: 0000000000000000 x13: 2e656572662d7265 x12: ffff80008283ef78 x11: ffff80008257efd0 x10: ffff80008283efd0 x9 : ffff80008021ed90 x8 : 0000000000000001 x7 : 00000000000bffe8 x6 : c0000000ffff7fff x5 : ffff0001fb8e3408 x4 : 0000000000000000 x3 : ffff800179993000 x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff000133d51600 Call trace: refcount_warn_saturate+0xf4/0x148 mlx5_core_put_rsc+0x88/0xa0 [mlx5_ib] mlx5_core_destroy_rq_tracked+0x64/0x98 [mlx5_ib] mlx5_ib_destroy_wq+0x34/0x80 [mlx5_ib] ib_destroy_wq_user+0x30/0xc0 [ib_core] uverbs_free_wq+0x28/0x58 [ib_uverbs] destroy_hw_idr_uobject+0x34/0x78 [ib_uverbs] uverbs_destroy_uobject+0x48/0x240 [ib_uverbs] __uverbs_cleanup_ufile+0xd4/0x1a8 [ib_uverbs] uverbs_destroy_ufile_hw+0x48/0x120 [ib_uverbs] ib_uverbs_close+0x2c/0x100 [ib_uverbs] __fput+0xd8/0x2f0 __fput_sync+0x50/0x70 __arm64_sys_close+0x40/0x90 invoke_syscall.constprop.0+0x74/0xd0 do_el0_svc+0x48/0xe8 el0_svc+0x44/0x1d0 el0t_64_sync_handler+0x120/0x130 el0t_64_sync+0x1a4/0x1a8

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 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.2%
EPSS %ILE
7th
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 (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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 3, 2025

Last Modified

October 15, 2026

Advisory Details (9)

Auto-updated Aug 2, 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/mlx5: Fix error flow upon firmware failure for RQ destruction - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/mlx5: Fix error flow upon firmware failure for RQ destruction - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/mlx5: Fix error flow upon firmware failure for RQ destruction - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7c4c84cdcc19e89d42f6bf117238e5471173423e
Web page

RDMA/mlx5: Fix error flow upon firmware failure for RQ destruction - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5d2ea5aebbb2f3ebde4403f9c55b2b057e5dd2d6
Web page

RDMA/mlx5: Fix error flow upon firmware failure for RQ destruction - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/50ac361ff8914133e3cf6ef184bac90c22cb8d79
Web page

RDMA/mlx5: Fix error flow upon firmware failure for RQ destruction - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/26d2f662d3a6655a82fd8a287e8b1ce471567f36
Web page

RDMA/mlx5: Fix error flow upon firmware failure for RQ destruction - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0a7790cbba654e925243571cf2f24d61603d3ed3

Vendor Advisories for CVE-2025-38161(1)

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-virtual-hwe-24.04-edge (6.14.0-32.32) @ plucky2026-10-15ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.156.166~20.04.1) @ focal2026-10-15ubuntu
ubuntulinux-tools-gcp-fips-5.15 (5.15.0.1092.82) @ jammy2026-10-15ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1090.96~20.04.1) @ focal2026-10-15ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1041.42~22.04.1) @ jammy2026-10-15ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-32.32~24.04.1) @ noble2026-10-15ubuntu
ubuntulinux-tools-raspi-6.14 (6.14.0-1014.14) @ plucky2026-10-15ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1047.50~22.04.2) @ jammy2026-10-15ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1041.42) @ noble2026-10-15ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-100.100+fips1) @ noble2026-10-15ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1043.44) @ noble2026-10-15ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1047.50+fips1) @ noble2026-10-15ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-100.100~22.04.1) @ jammy2026-10-15ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1046.49.1) @ noble2026-10-15ubuntu
ubuntulinux-tools-ibm-lts-24.04 (6.8.0-1044.44) @ noble2026-10-15ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1023.24) @ noble2026-10-15ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1046.52) @ noble2026-10-15ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1046.52+fips1) @ noble2026-10-15ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-10-15ubuntu
ubuntulinux-tools-azure-6.14 (6.14.0-1012.12) @ plucky2026-10-15ubuntu
ubuntulinux-tools-oem-6.14 (6.14.0-1012.12) @ noble2026-10-15ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.14.0-1012.12~24.04.1) @ noble2026-10-15ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1096.94) @ jammy2026-10-15ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1096.105~20.04.1) @ focal2026-10-15ubuntu
ubuntulinux-tools-nvidia-tegra-igx-rt-5.15 (5.15.0.1034.36) @ jammy2026-10-15ubuntu
ubuntulinux-tools-kvm-5.15 (5.15.0.1088.84) @ jammy2026-10-15ubuntu
ubuntulinux-tools-oracle-edge (6.14.0-1013.13~24.04.1) @ noble2026-10-15ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1096.81) @ jammy2026-10-15ubuntu
ubuntulinux-tools-realtime-5.15 (5.15.0.1092.96) @ jammy2026-10-15ubuntu
ubuntulinux-virtual-6.8 (6.8.0-100.100) @ noble2026-10-15ubuntu
linuxKernel @ 5.10.239 (fixes >=4.5.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

(24)

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 8× in last 7d / 40× 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 191 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 93 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-38161?
CVE-2025-38161 is a medium-severity vulnerability; its CVE record was published on July 3, 2025. In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix error flow upon firmware failure for RQ destruction Upon RQ destruction if the firmware command fails which is the last resource to be destroyed some SW resources were already cleaned regardless of the failure. Now…
When was the CVE record for CVE-2025-38161 published?
The CVE record for CVE-2025-38161 was published on July 3, 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 October 15, 2026; the record at its source may have been updated since.
Is CVE-2025-38161 actively exploited?
CVE-2025-38161 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (7th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-38161?
CVE-2025-38161 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-38161?
A fix for CVE-2025-38161 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-38161 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-38161

Explore →

Is Your Infrastructure Affected by CVE-2025-38161?

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

Book a Demo →Browse All CVEs