CVE-2026-98360
Received Received - Intake

Race Condition in Linux Kernel RDMA RXE Module Leads to Use-After-Free

Vulnerability report for CVE-2026-98360, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-06

Last updated on: 2026-10-06

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: insert mcg into mcg_tree only after rxe_mcast_add() succeeds rxe_get_mcg() publishes a newly allocated multicast group in rxe->mcg_tree before programming the backing Ethernet multicast address with rxe_mcast_add(), which runs outside mcg_lock. A local userspace RDMA client reaches this path with ATTACH_MCAST on a UD QP; if rxe_mcast_add() then returns an error (for example -ENODEV when the backing netdev has been removed, or a propagated dev_mc_add() error), the unwind frees the published group without removing it from the tree. A later lookup of the same MGID dereferences the freed struct rxe_mcg from __rxe_lookup_mcg(). Fix this by keeping the new mcg private until rxe_mcast_add() succeeds. Split the tree publication into __rxe_publish_mcg(), call rxe_mcast_add() before taking the tree reference, and free the still-private mcg on failure. Because the group is never visible in mcg_tree until the multicast address is programmed, no concurrent caller can look it up or attach a QP to a group that is about to be torn down, so the error path needs no conditional unwind. If another caller publishes the same MGID while the address is being programmed, the post-add re-check under mcg_lock finds the winner; this caller then drops its private object and balances its own rxe_mcast_add() with rxe_mcast_del() before returning the winner. Reproduced by forcing the rxe_mcast_add() error return under KASAN: without the change the next attach to the same MGID reports a slab-use-after-free in __rxe_lookup_mcg(); with it the forced failure returns cleanly. A no-injection attach/detach regression, including a two-QP shared join/leave and re-attach, stays KASAN- and leak-clean.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-06
Last Modified
2026-10-06
Generated
2026-10-06
AI Q&A
2026-10-06
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 7 associated CPEs
Vendor Product Version / Range
Linux Linux a926a903b7dc39a8a949150258c09290998dd812
Linux Linux a926a903b7dc39a8a949150258c09290998dd812
Linux Linux a926a903b7dc39a8a949150258c09290998dd812
Linux Linux a926a903b7dc39a8a949150258c09290998dd812
Linux Linux a926a903b7dc39a8a949150258c09290998dd812
Linux Linux a926a903b7dc39a8a949150258c09290998dd812
Linux Linux 5.18

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel involves a race condition in the RDMA/rxe subsystem. A multicast group (mcg) is incorrectly inserted into a tree structure before its backing Ethernet multicast address is properly programmed. If an error occurs during address programming, the group is freed without removal from the tree, leading to a use-after-free vulnerability when another process later attempts to access the freed memory.

Detection Guidance

This vulnerability is specific to the Linux kernel's RDMA/rxe subsystem and requires kernel-level detection. There are no direct user-space commands to detect it. Monitoring for slab-use-after-free errors in kernel logs or using tools like KASAN (Kernel Address Sanitizer) during RDMA operations may help identify exploitation attempts.

Impact Analysis

This vulnerability could allow a local userspace RDMA client to trigger a use-after-free condition, potentially causing system crashes, memory corruption, or privilege escalation. Attackers with local access could exploit this to execute arbitrary code or disrupt services running on affected systems.

Mitigation Strategies

Apply the kernel patch that fixes this issue by ensuring multicast groups are only inserted into the tree after rxe_mcast_add() succeeds. Update to a patched kernel version where this flaw is resolved. If immediate patching is not possible, disable the RDMA/rxe subsystem if not in use to reduce attack surface.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-98360. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart