CVE-2025-38022

NVD 0.07.8
EchelonGraph scoreLOW confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-06-18.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 0%CVSS: Exploit: NoneExposed: 0

A fix is available — apply it.

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

RDMA/core: Fix "KASAN: slab-use-after-free Read in ib_register_device" problem

Call Trace:

__dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:408 [inline] print_report+0xc3/0x670 mm/kasan/report.c:521 kasan_report+0xe0/0x110 mm/kasan/report.c:634 strlen+0x93/0xa0 lib/string.c:420 __fortify_strlen include/linux/fortify-string.h:268 [inline] get_kobj_path_length lib/kobject.c:118 [inline] kobject_get_path+0x3f/0x2a0 lib/kobject.c:158 kobject_uevent_env+0x289/0x1870 lib/kobject_uevent.c:545 ib_register_device drivers/infiniband/core/device.c:1472 [inline] ib_register_device+0x8cf/0xe00 drivers/infiniband/core/device.c:1393 rxe_register_device+0x275/0x320 drivers/infiniband/sw/rxe/rxe_verbs.c:1552 rxe_net_add+0x8e/0xe0 drivers/infiniband/sw/rxe/rxe_net.c:550 rxe_newlink+0x70/0x190 drivers/infiniband/sw/rxe/rxe.c:225 nldev_newlink+0x3a3/0x680 drivers/infiniband/core/nldev.c:1796 rdma_nl_rcv_msg+0x387/0x6e0 drivers/infiniband/core/netlink.c:195 rdma_nl_rcv_skb.constprop.0.isra.0+0x2e5/0x450 netlink_unicast_kernel net/netlink/af_netlink.c:1313 [inline] netlink_unicast+0x53a/0x7f0 net/netlink/af_netlink.c:1339 netlink_sendmsg+0x8d1/0xdd0 net/netlink/af_netlink.c:1883 sock_sendmsg_nosec net/socket.c:712 [inline] __sock_sendmsg net/socket.c:727 [inline] ____sys_sendmsg+0xa95/0xc70 net/socket.c:2566 ___sys_sendmsg+0x134/0x1d0 net/socket.c:2620 __sys_sendmsg+0x16d/0x220 net/socket.c:2652 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcd/0x260 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f

This problem is similar to the problem that the commit 1d6a9e7449e2 ("RDMA/core: Fix use-after-free when rename device name") fixes.

The root cause is: the function ib_device_rename() renames the name with lock. But in the function kobject_uevent(), this name is accessed without lock protection at the same time.

The solution is to add the lock protection when this name is accessed in the function kobject_uevent().

CVSS v3
EG Score
7.8(low)
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
6.1%
KEV
Not listed

Published

June 18, 2025

Last Modified

June 11, 2026

Patch Availability(30)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1049.50) @ noble2026-05-30ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2042.43) @ noble2026-05-30ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1047.48) @ noble2026-05-30ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1054.57+fips1) @ noble2026-05-30ubuntu
ubuntulinux-tools-nvidia-64k-6.8 (6.8.0-1051.54) @ noble2026-05-30ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1051.54.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1054.57~22.04.1) @ jammy2026-05-30ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1054.60) @ noble2026-05-30ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1029.30) @ noble2026-05-30ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1022.22) @ noble2026-05-30ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1054.60+fips1) @ noble2026-05-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-28.28~24.04.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1110.119~20.04.1) @ focal2026-05-30ubuntu
ubuntulinux-tools-azure-6.14 (6.14.0-1010.10) @ plucky2026-05-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-28.28) @ plucky2026-05-30ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1067 (5.15.0-1067.71) @ jammy2026-05-30ubuntu
redhatkernel-0:4.18.0-193.187.1.el8_22026-02-26redhat
redhatkernel-0:4.18.0-305.186.1.el8_42026-02-25redhat
redhatkernel-rt-0:5.14.0-70.167.1.rt21.239.el9_02026-02-25redhat
redhatkernel-0:5.14.0-70.167.1.el9_02026-02-25redhat
redhatkernel-0:4.18.0-372.181.1.el8_62026-02-25redhat
redhatkernel-0:5.14.0-427.110.1.el9_42026-02-12redhat
redhatkernel-0:4.18.0-477.128.1.el8_82026-02-11redhat
redhatkernel-rt-0:5.14.0-284.156.1.rt14.441.el9_22026-02-11redhat
redhatkernel-0:5.14.0-284.156.1.el9_22026-02-11redhat
redhatkernel-0:5.14.0-570.86.1.el9_62026-02-09redhat
redhatkernel-0:5.14.0-611.30.1.el9_72026-02-09redhat
redhatkernel-rt-0:4.18.0-553.100.1.rt7.441.el8_102026-02-02redhat
redhatkernel-0:6.12.0-124.31.1.el10_12026-02-02redhat
redhatkernel-0:4.18.0-553.100.1.el8_102026-02-02redhat

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.

Weakness Classification(1)

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

Additional Vendor Advisories

(12)

Data Freshness Timeline

(refreshed 12× in last 7d / 45× 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.

  1. 2026-07-23 02:54 UTCEG score recompute
  2. 2026-07-22 14:07 UTCEPSS rescore
  3. 2026-07-22 14:07 UTCEPSS rescore
  4. 2026-07-21 15:24 UTCEPSS rescore
  5. 2026-07-20 17:07 UTCEPSS rescore
  6. 2026-07-19 14:30 UTCEPSS rescore
  7. 2026-07-19 14:30 UTCEPSS rescore
  8. 2026-07-19 02:28 UTCEPSS rescore
  9. 2026-07-19 02:28 UTCEPSS rescore
  10. 2026-07-18 10:04 UTCEPSS rescore
  11. 2026-07-18 10:04 UTCEPSS rescore
  12. 2026-07-16 17:02 UTCEPSS rescore
  13. 2026-07-15 16:57 UTCEPSS rescore
  14. 2026-07-15 16:57 UTCEPSS rescore
  15. 2026-07-15 01:59 UTCEPSS rescore
  16. 2026-07-15 01:59 UTCEPSS rescore
  17. 2026-07-13 06:12 UTCEPSS rescore
  18. 2026-07-12 05:46 UTCEPSS rescore
  19. 2026-07-09 19:09 UTCEPSS rescore
  20. 2026-07-09 19:09 UTCEPSS rescore
  21. 2026-07-07 13:45 UTCEPSS rescore
  22. 2026-07-06 22:34 UTCOSV refresh
  23. 2026-07-06 16:27 UTCEPSS rescore
  24. 2026-07-06 16:27 UTCEPSS rescore
  25. 2026-07-06 02:23 UTCEPSS rescore
Show 59 more
  1. 2026-07-05 02:30 UTCEPSS rescore
  2. 2026-07-04 06:30 UTCEPSS rescore
  3. 2026-07-01 15:06 UTCEPSS rescore
  4. 2026-07-01 15:06 UTCEPSS rescore
  5. 2026-06-30 23:22 UTCEPSS rescore
  6. 2026-06-30 23:22 UTCEPSS rescore
  7. 2026-06-29 14:06 UTCEPSS rescore
  8. 2026-06-29 14:06 UTCEPSS rescore
  9. 2026-06-28 14:07 UTCEPSS rescore
  10. 2026-06-28 14:07 UTCEPSS rescore
  11. 2026-06-28 04:55 UTCEPSS rescore
  12. 2026-06-28 04:55 UTCEPSS rescore
  13. 2026-06-27 03:08 UTCEPSS rescore
  14. 2026-06-27 03:08 UTCEPSS rescore
  15. 2026-06-25 13:49 UTCEPSS rescore
  16. 2026-06-25 13:49 UTCEPSS rescore
  17. 2026-06-24 14:04 UTCEPSS rescore
  18. 2026-06-24 14:04 UTCEPSS rescore
  19. 2026-06-23 21:32 UTCEPSS rescore
  20. 2026-06-23 21:32 UTCEPSS rescore
  21. 2026-06-22 14:25 UTCEPSS rescore
  22. 2026-06-22 14:25 UTCEPSS rescore
  23. 2026-06-21 14:56 UTCEPSS rescore
  24. 2026-06-21 14:56 UTCEPSS rescore
  25. 2026-06-21 01:59 UTCEPSS rescore
  26. 2026-06-21 01:59 UTCEPSS rescore
  27. 2026-06-19 19:25 UTCEPSS rescore
  28. 2026-06-19 19:25 UTCEPSS rescore
  29. 2026-06-18 17:52 UTCEPSS rescore
  30. 2026-06-18 17:52 UTCEPSS rescore
  31. 2026-06-18 09:43 UTCOSV refresh
  32. 2026-06-14 23:17 UTCEPSS rescore
  33. 2026-06-14 23:13 UTCMITRE cvelistV5
  34. 2026-06-13 23:00 UTCEPSS rescore
  35. 2026-06-12 23:11 UTCEPSS rescore
  36. 2026-06-11 14:00 UTCEPSS rescore
  37. 2026-06-10 22:18 UTCEPSS rescore
  38. 2026-06-10 13:22 UTCEPSS rescore
  39. 2026-06-08 14:16 UTCEPSS rescore
  40. 2026-06-08 14:16 UTCEPSS rescore
  41. 2026-06-07 15:24 UTCEPSS rescore
  42. 2026-06-06 13:47 UTCEPSS rescore
  43. 2026-06-06 13:47 UTCEPSS rescore
  44. 2026-06-05 22:46 UTCEPSS rescore
  45. 2026-06-05 22:46 UTCEPSS rescore
  46. 2026-06-05 06:10 UTCEPSS rescore
  47. 2026-06-05 06:10 UTCEPSS rescore
  48. 2026-06-04 13:12 UTCEPSS rescore
  49. 2026-06-04 13:12 UTCEPSS rescore
  50. 2026-06-02 20:12 UTCEPSS rescore
  51. 2026-06-01 13:51 UTCEPSS rescore
  52. 2026-06-01 13:51 UTCEPSS rescore
  53. 2026-05-31 22:30 UTCEPSS rescore
  54. 2026-05-31 22:30 UTCEPSS rescore
  55. 2026-05-31 00:16 UTCEPSS rescore
  56. 2026-05-30 03:29 UTCEG score recompute
  57. 2026-05-30 03:29 UTCVendor advisory
  58. 2026-05-30 03:28 UTCGHSA enrichment
  59. 2026-05-29 13:44 UTCEPSS rescore

Frequently asked(4)

What is CVE-2025-38022?
CVE-2025-38022 is a publicly disclosed vulnerability published on June 18, 2025. In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Fix "KASAN: slab-use-after-free Read in ibregisterdevice" problem Call Trace: dumpstack lib/dumpstack.c:94 [inline] dumpstacklvl+0x116/0x1f0 lib/dump_stack.c:120 printaddressdescription mm/kasan/report.c:408 [inline]…
When was CVE-2025-38022 disclosed?
CVE-2025-38022 was first published in the National Vulnerability Database on June 18, 2025, with the most recent update on June 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-38022 actively exploited?
CVE-2025-38022 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 6.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2025-38022?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-38022, 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

Explore the affected products and dependency analysis for CVE-2025-38022

Explore →

Is Your Infrastructure Affected by CVE-2025-38022?

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