LiveActive security incident?Get immediate response
CVE Record

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

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: <TASK> __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.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A flaw in Linux’s software RDMA-over-Ethernet component can access memory after it has been freed during failed queue creation. A local low-privileged user may be able to trigger it without user interaction. The supplied CVSS rating is 7.8, reflecting potentially serious confidentiality, integrity, and availability impact, although the bundle provides no confirmed real-world exploitation.

Executive priority

Treat this as a high-priority kernel maintenance issue on shared Linux hosts using software RoCE, especially where untrusted users or containers can access RDMA interfaces. For systems without RXE exposure, urgency is lower but package status should still be checked. There is no supplied evidence of active exploitation requiring emergency incident response.

Technical view

When rxe_cq_from_init fails inside rxe_create_cq, it frees some resources before rxe_cleanup runs. The later cleanup reaches rxe_queue_cleanup and reads freed slab memory. The kernel fix assigns all resource cleanup to rxe_cleanup, preventing inconsistent ownership on the error path. The reported path is reachable through the local RDMA uverbs create-completion-queue interface.

Likely exposure

Exposure is most likely on Linux systems where RXE, also known as software RoCE, is available and accessible to local users or workloads. Internet reachability alone does not create the stated attack path. The bundle’s flattened version data is ambiguous, so administrators should verify distribution package status rather than infer vulnerability from the displayed version list alone.

Exploitation context

The supplied vector indicates a local, low-complexity attack requiring low privileges and no user interaction. No remote attack path is documented. This CVE is not marked as CISA KEV, and the supplied sources provide no evidence of active exploitation or a public proof of concept. Practical exploitability and reliable impact are not established by the bundle.

Researcher notes

The report documents a cleanup-ownership error exposed during failed completion-queue initialization and detected as a slab use-after-free read. Although CVSS assigns high impact across confidentiality, integrity, and availability, the bundle does not demonstrate those outcomes or identify a CWE. Assess reachability through RXE configuration, device permissions, namespaces, and distribution backports before concluding exploitability.

Mitigation direction

  • Install a vendor kernel update containing the fix for the system’s supported kernel branch.
  • Prioritize multi-user systems exposing RDMA uverbs or software RoCE to untrusted workloads.
  • If patching is delayed, restrict RXE access or disable unused software RoCE where operationally safe.
  • Consult distribution advisories for package-specific remediation and reboot requirements.

Validation and detection

  • Inventory running kernel releases and distribution package build identifiers.
  • Determine whether RXE software RoCE and RDMA uverbs are present, enabled, or actively used.
  • Confirm the installed package includes the applicable upstream stable fix or distribution backport.
  • After updating, verify the fixed kernel is running and RDMA-dependent workloads operate normally.
  • Review kernel diagnostics for the documented rxe_queue_cleanup use-after-free signature.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-38024 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
2ADP providers
11Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2025-38024Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux8700e3e7c4857d28ebaa824509934556da0b3e76, 8700e3e7c4857d28ebaa824509934556da0b3e76, 8700e3e7c4857d28ebaa824509934556da0b3e76, 8700e3e7c4857d28ebaa824509934556da0b3e76, 8700e3e7c4857d28ebaa824509934556da0b3e76, 8700e3e7c4857d28ebaa824509934556da0b3e76, 8700e3e7c4857d28ebaa824509934556da0b3e76, 8700e3e7c4857d28ebaa824509934556da0b3e76unaffected
LinuxLinux4.8, 0, 5.4.294, 5.10.238, 5.15.184, 6.1.140, 6.6.92, 6.12.30, 6.14.8, 6.15affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.