Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

HighCVSS 7.8 · v3.1—No exploit Fix available

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.20% (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 03df57ad4b0ff9c5a93ff981aba0b42578ad1571, 10c7f1c647da3b77ef8827d974a97b6530b64df0, 17d3103325e891e10994e7aa28d12bea04dc2c60.

Low priority for now. Upgrade to Linux Linux 03df57ad4b0ff9c5a93ff981aba0b42578ad1571, 10c7f1c647da3b77ef8827d974a97b6530b64df0, 17d3103325e891e10994e7aa28d12bea04dc2c60 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/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().

Published
Jun 18, 2025
Updated
Aug 5, 2026
EPSS
0.2% · 10th 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.2%

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

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

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 every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE 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, at most 30 a day (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
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

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

    • 9b54e31fd08f8d8db507d021c88e760d5f8e4640, 5.11affected
    • 53e9a5a692f839780084ad81dbd461ec917f74f7 and later · before ba467b6870ea2a73590478d9612d6ea1dcdd68b7affected · git
    • 779e0bf47632c609c59f527f9711ecd3214dccb0 and later · before 5629064f92f0de6d6b3572055cd35361c3ad953caffected · git
    • 779e0bf47632c609c59f527f9711ecd3214dccb0 and later · before 312dae3499106ec8cb7442ada12be080aa9fbc3baffected · git
    • 779e0bf47632c609c59f527f9711ecd3214dccb0 and later · before 17d3103325e891e10994e7aa28d12bea04dc2c60affected · git
    • 779e0bf47632c609c59f527f9711ecd3214dccb0 and later · before 10c7f1c647da3b77ef8827d974a97b6530b64df0affected · git
    • 779e0bf47632c609c59f527f9711ecd3214dccb0 and later · before 03df57ad4b0ff9c5a93ff981aba0b42578ad1571affected · git
    • 779e0bf47632c609c59f527f9711ecd3214dccb0 and later · before d0706bfd3ee40923c001c6827b786a309e2a8713affected · git
    • 5.10.4 and later · before 5.10.248affected · semver
    • 5.4.86 and later · before 5.5affected · 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-124.31.1.el10_16.12.0-124.31.1.el10_1
AlmaLinux:10kernel-docbefore 6.12.0-124.31.1.el10_16.12.0-124.31.1.el10_1
AlmaLinux:8bpftoolbefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.100.1.rt7.441.el8_104.18.0-553.100.1.rt7.441.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.100.1.rt7.441.el8_104.18.0-553.100.1.rt7.441.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.100.1.rt7.441.el8_104.18.0-553.100.1.rt7.441.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.100.1.rt7.441.el8_104.18.0-553.100.1.rt7.441.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.100.1.rt7.441.el8_104.18.0-553.100.1.rt7.441.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.100.1.rt7.441.el8_104.18.0-553.100.1.rt7.441.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.100.1.rt7.441.el8_104.18.0-553.100.1.rt7.441.el8_10

+96

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-38019Jun 18, 2025 · mlxsw: spectrum_router: Fix use-after-free when deleting GRE net devices
    31Monitor
  • ← EarlierCVE-2025-38021Jun 18, 2025 · drm/amd/display: Fix null check of pipe_ctx->plane_state for update_dchubp_dpp
    22Monitor
  • Later →CVE-2025-38024Jun 18, 2025 · RDMA/rxe: Fix slab-use-after-free Read in rxe_queue_cleanup bug
    31Monitor

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 Linux03df57ad4b0ff9c5a93ff981aba0b42578ad1571Vendor (CNA)
Linux Linux10c7f1c647da3b77ef8827d974a97b6530b64df0Vendor (CNA)
Linux Linux17d3103325e891e10994e7aa28d12bea04dc2c60Vendor (CNA)
Linux Linux312dae3499106ec8cb7442ada12be080aa9fbc3bVendor (CNA)
Linux Linux5.10.248Vendor (CNA)
Linux Linux5.5Vendor (CNA)
Linux Linux5629064f92f0de6d6b3572055cd35361c3ad953cVendor (CNA)
Linux Linuxba467b6870ea2a73590478d9612d6ea1dcdd68b7Vendor (CNA)
Linux Linuxd0706bfd3ee40923c001c6827b786a309e2a8713Vendor (CNA)
almalinux:bpftool4.18.0-553.100.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.100.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt4.18.0-553.100.1.rt7.441.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-core4.18.0-553.100.1.rt7.441.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug4.18.0-553.100.1.rt7.441.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-core4.18.0-553.100.1.rt7.441.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-devel4.18.0-553.100.1.rt7.441.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules4.18.0-553.100.1.rt7.441.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules-extra4.18.0-553.100.1.rt7.441.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-devel4.18.0-553.100.1.rt7.441.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules4.18.0-553.100.1.rt7.441.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules-extra4.18.0-553.100.1.rt7.441.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.162-1 · Debian:12Package registry (OSV)
debian:linux-6.16.1.162-1~deb11u1 · Debian:11Package registry (OSV)
red hat:kernel-rt0:4.18.0-553.100.1.rt7.441.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-core0:4.18.0-553.100.1.rt7.441.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-core0:4.18.0-553.100.1.rt7.441.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-debuginfo0:4.18.0-553.100.1.rt7.441.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-devel0:4.18.0-553.100.1.rt7.441.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-kvm0:4.18.0-553.100.1.rt7.441.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-modules0:4.18.0-553.100.1.rt7.441.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)

+7

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.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

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.

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.

References

All records