CVE-2026-72468

CVE CVE-2026-72468EUVD EUVD-2026-59367Published 2026-08-15T05:57:11.000ZLast changed 2026-08-17T05:15:13.000Z

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: xprtrdma: Initialize re_id before removal registration rpcrdma_create_id() registers ep->re_rn with the rpcrdma ib_client before returning the new rdma_cm_id to rpcrdma_ep_create(). However rpcrdma_ep_create() currently stores that pointer in ep->re_id only after rpcrdma_create_id() returns. A local administrator can race an NFS/RDMA mount against RDMA device removal. If rpcrdma_remove_one() observes the just-registered notification before rpcrdma_ep_create() assigns ep->re_id, rpcrdma_ep_removal_done() calls trace_xprtrdma_device_removal(NULL). The tracepoint dereferences id->device->name and copies id->route.addr.dst_addr, so the callback can crash the kernel with a NULL pointer dereference. Store the rdma_cm_id in ep->re_id immediately before publishing ep->re_rn. The existing error path still destroys the id directly if registration fails; ep is then freed by the caller without using ep->re_id. Remove the later duplicate assignment in rpcrdma_ep_create().

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux patch: 6.18.40; 3f4eb9ff923413cdb4c7e171c06d3564f6286712 <28743571c17b58c21a7216fc9faaf8028df5869b; patch: 7.2; 3f4eb9ff923413cdb4c7e171c06d3564f6286712 <bb7caa63e1db22fd03e8dc591b12169e99169dff; patch: 6.12.97; 3f4eb9ff923413cdb4c7e171c06d3564f6286712 <264ccd7871915749bee55fe0c39467a7f08d5479; patch: 7.1.5; 3f4eb9ff923413cdb4c7e171c06d3564f6286712 <51248d877bbc6e604e38aeaf776c2781cb4f0dbd; patch: 0; 6.11

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.