PoC Monitor
← All CVEs
CVE-2026-98360published 6 Oct 2026 08:46 UTCData: JSON · API

Linux

RDMA/rxe: insert mcg into mcg_tree only after rxe_mcast_add() succeeds

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.0high · scored by CNA
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Linux Linux
  • >= a926a903b7dc39a8a949150258c09290998dd812, < ddb43ac0926d4a931bc9b7744b93627f627457e5
  • >= a926a903b7dc39a8a949150258c09290998dd812, < c79a789aa15180a1543b5db49c343d12e3ec214d
  • >= a926a903b7dc39a8a949150258c09290998dd812, < faae1fb4ccf8205806a8802c008798dabeb0205b
  • >= a926a903b7dc39a8a949150258c09290998dd812, < 02c0a2fa69c16248a7432af8a6d64ab2a73a5283
  • >= a926a903b7dc39a8a949150258c09290998dd812, < d4fc4e37f8a143b0fe83b42c8fb48cf542154fee
  • >= a926a903b7dc39a8a949150258c09290998dd812, < 1caceeb2d74bbe88223aea55eb8626b4c5f076fd

Fixed in ddb43ac0926d4a931bc9b7744b93627f627457e5, c79a789aa15180a1543b5db49c343d12e3ec214d, faae1fb4ccf8205806a8802c008798dabeb0205b, 02c0a2fa69c16248a7432af8a6d64ab2a73a5283, d4fc4e37f8a143b0fe83b42c8fb48cf542154fee, 1caceeb2d74bbe88223aea55eb8626b4c5f076fd

Linux Linux
  • 5.18

Fixed in 0, 6.1.189, 6.6.158, 6.12.112, 6.18.54, 7.2.8, 7.3

Mitigation

Upgrade Linux to ddb43ac0926d4a931bc9b7744b93627f627457e5 or c79a789aa15180a1543b5db49c343d12e3ec214d or faae1fb4ccf8205806a8802c008798dabeb0205b or 02c0a2fa69c16248a7432af8a6d64ab2a73a5283 or d4fc4e37f8a143b0fe83b42c8fb48cf542154fee or 1caceeb2d74bbe88223aea55eb8626b4c5f076fd or later.

Upgrade Linux to 0 or 6.1.189 or 6.6.158 or 6.12.112 or 6.18.54 or 7.2.8 or 7.3 or later.

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published6 Oct 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.