CVE-2025-38024

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

RDMA/rxe: Fix slab-use-after-free Read in rxe_queue_cleanup bug

Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x7d/0xa0 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xcf/0x610 mm/kasan/report.c:489 kasan_report+0xb5/0xe0 mm/kasan/report.c:602 rxe_queue_cleanup+0xd0/0xe0 drivers/infiniband/sw/rxe/rxe_queue.c:195 rxe_cq_cleanup+0x3f/0x50 drivers/infiniband/sw/rxe/rxe_cq.c:132 __rxe_cleanup+0x168/0x300 drivers/infiniband/sw/rxe/rxe_pool.c:232 rxe_create_cq+0x22e/0x3a0 drivers/infiniband/sw/rxe/rxe_verbs.c:1109 create_cq+0x658/0xb90 drivers/infiniband/core/uverbs_cmd.c:1052 ib_uverbs_create_cq+0xc7/0x120 drivers/infiniband/core/uverbs_cmd.c:1095 ib_uverbs_write+0x969/0xc90 drivers/infiniband/core/uverbs_main.c:679 vfs_write fs/read_write.c:677 [inline] vfs_write+0x26a/0xcc0 fs/read_write.c:659 ksys_write+0x1b8/0x200 fs/read_write.c:731 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xaa/0x1b0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f

In the function rxe_create_cq, when rxe_cq_from_init fails, the function rxe_cleanup will be called to handle the allocated resources. In fact, some memory resources have already been freed in the function rxe_cq_from_init. Thus, this problem will occur.

The solution is to let rxe_cleanup do all the work.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

June 18, 2025

Last Modified

August 5, 2026

Advisory Details (10)

Auto-updated Jul 31, 2026
Patch available.
generic Patch Available

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

https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html
generic Patch Available

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

https://lists.debian.org/debian-lts-announce/2025/08/msg00010.html
generic

RDMA/rxe: Fix slab-use-after-free Read in rxe_queue_cleanup bug - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f8f470e3a757425a8f98fb9a5991e3cf62fc7134
generic

RDMA/rxe: Fix slab-use-after-free Read in rxe_queue_cleanup bug - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f81b33582f9339d2dc17c69b92040d3650bb4bae
generic

RDMA/rxe: Fix slab-use-after-free Read in rxe_queue_cleanup bug - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ee4c5a2a38596d548566560c0c022ab797e6f71a
generic

RDMA/rxe: Fix slab-use-after-free Read in rxe_queue_cleanup bug - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7c7c80c32e00665234e373ab03fe82f5c5c2c230
generic

RDMA/rxe: Fix slab-use-after-free Read in rxe_queue_cleanup bug - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/52daccfc3fa68ee1902d52124921453d7a335591
generic

RDMA/rxe: Fix slab-use-after-free Read in rxe_queue_cleanup bug - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3a3b73e135e3bd18423d0baa72571319c7feb759
generic

RDMA/rxe: Fix slab-use-after-free Read in rxe_queue_cleanup bug - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/336edd6b0f5b7fbffc3e065285610624f59e88df
generic

RDMA/rxe: Fix slab-use-after-free Read in rxe_queue_cleanup bug - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/16c45ced0b3839d3eee72a86bb172bef6cf58980

Patch Availability(31)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1094.79) @ jammy2026-05-30ubuntu
ubuntulinux-tools-azure-6.14 (6.14.0-1010.10) @ plucky2026-05-30ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1094.103~20.04.1) @ focal2026-05-30ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1047.50~22.04.2) @ jammy2026-05-30ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-100.100+fips1) @ noble2026-05-30ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1041.42~22.04.1) @ jammy2026-05-30ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1043.44) @ noble2026-05-30ubuntu
ubuntulinux-virtual-6.8 (6.8.0-100.100) @ noble2026-05-30ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1041.42) @ noble2026-05-30ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1047.50+fips1) @ noble2026-05-30ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-100.100~22.04.1) @ jammy2026-05-30ubuntu
ubuntulinux-tools-gke-64k-6.8 (6.8.0-1043.48) @ noble2026-05-30ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-100.100.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1046.49.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-ibm-lts-24.04 (6.8.0-1044.44) @ noble2026-05-30ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1046.52) @ noble2026-05-30ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1023.24) @ noble2026-05-30ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1046.52+fips1) @ noble2026-05-30ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-05-30ubuntu
redhatkernel-0:4.18.0-477.143.1.el8_82026-05-20redhat
redhatkernel-rt-0:3.10.0-1160.148.1.rt56.1300.el72026-04-27redhat
redhatkernel-0:3.10.0-1160.148.1.el72026-04-22redhat
redhatkernel-0:4.18.0-372.185.1.el8_62026-03-25redhat
redhatkernel-0:4.18.0-193.190.1.el8_22026-03-25redhat
redhatkernel-0:4.18.0-305.187.1.el8_42026-03-25redhat
redhatkernel-0:5.14.0-427.114.1.el9_42026-03-11redhat
redhatkernel-0:5.14.0-570.96.1.el9_62026-03-09redhat
redhatkernel-0:5.14.0-611.30.1.el9_72026-02-09redhat
redhatkernel-0:4.18.0-553.100.1.el8_102026-02-02redhat
redhatkernel-rt-0:4.18.0-553.100.1.rt7.441.el8_102026-02-02redhat
linuxKernel @ 5.4.294osv

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 rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (46 versions)5.10.244-1
linux-6.16.1.106-3~deb11u1 ... 6.1.137-1~deb11u1 (8 versions)6.1.140-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (40 versions)6.1.140-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.30-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.30-1

Weakness Classification(1)

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

Additional Vendor Advisories

(14)

Data Freshness Timeline

(refreshed 5× in last 7d / 26× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 139 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2025-38024?
CVE-2025-38024 is a high vulnerability published on June 18, 2025. In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix slab-use-after-free Read in rxequeuecleanup bug Call Trace: <TASK> dumpstack lib/dumpstack.c:94 [inline] dumpstacklvl+0x7d/0xa0 lib/dump_stack.c:120 printaddressdescription mm/kasan/report.c:378 [inline]…
When was CVE-2025-38024 disclosed?
CVE-2025-38024 was first published in the National Vulnerability Database on June 18, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-38024 actively exploited?
CVE-2025-38024 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 91.8% of all scored CVEs.
What is the CVSS score of CVE-2025-38024?
CVE-2025-38024 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-38024?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-38024, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2025-38024?

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