Kernel memory corruption via RDMA name race
Published Jun 18, 2025 · Updated Aug 5, 2026
Use-after-free in Linux kernel RDMA/core allows local users with CAP_NET_ADMIN to disclose or corrupt kernel memory through a device-name race. kobject_uevent reads an RDMA device name without the lock held by concurrent ib_device_rename operations, allowing the freed name allocation to be reused while it is copied into a uevent. Exploitation requires local access and CAP_NET_ADMIN in the initial user namespace; successful races can expose kernel data, corrupt kernel state, or interrupt the host.
Summary
What happened
Use-after-free in Linux kernel RDMA/core allows local users with CAP_NET_ADMIN to disclose or corrupt kernel memory through a device-name race. kobject_uevent reads an RDMA device name without the lock held by concurrent ib_device_rename operations, allowing the freed name allocation to be reused while it is copied into a uevent. Exploitation requires local access and CAP_NET_ADMIN in the initial user namespace; successful races can expose kernel data, corrupt kernel state, or interrupt the host.
The record
- CVE
- CVE-2025-38022
- Published
- Jun 18, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 18, 2025CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.10.4 <5.10.248
- Affected versionversion=5.11
- Affected versionversion=53e9a5a692f839780084ad81dbd461ec917f74f7 <ba467b6870ea2a73590478d9612d6ea1dcdd68b7
- Affected versionversion=5.4.86 <5.5
- Affected versionversion=779e0bf47632c609c59f527f9711ecd3214dccb0 <03df57ad4b0ff9c5a93ff981aba0b42578ad1571
- Affected versionversion=779e0bf47632c609c59f527f9711ecd3214dccb0 <10c7f1c647da3b77ef8827d974a97b6530b64df0
- Affected versionversion=779e0bf47632c609c59f527f9711ecd3214dccb0 <17d3103325e891e10994e7aa28d12bea04dc2c60
- Affected versionversion=779e0bf47632c609c59f527f9711ecd3214dccb0 <312dae3499106ec8cb7442ada12be080aa9fbc3b
- Affected versionversion=779e0bf47632c609c59f527f9711ecd3214dccb0 <5629064f92f0de6d6b3572055cd35361c3ad953c
- Affected versionversion=779e0bf47632c609c59f527f9711ecd3214dccb0 <d0706bfd3ee40923c001c6827b786a309e2a8713
- Affected versionversion=9b54e31fd08f8d8db507d021c88e760d5f8e4640
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo