Answer in brief
CVE-2026-72468 records a Unknown severity vulnerability in xprtrdma: Initialize re_id before removal registration. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3f4eb9ff923413cdb4c7e171c06d3564f6286712 <51248d877bbc6e604e38aeaf776c2781cb4f0dbd || >=3f4eb9ff923413cdb4c7e171c06d3564f6286712 <28743571c17b58c21a7216fc9faaf8028df5869b || >=3f4eb9ff923413cdb4c7e171c06d3564f6286712 <264ccd7871915749bee55fe0c39467a7f08d5479 || >=3f4eb9ff923413cdb4c7e171c06d3564f6286712 <bb7caa63e1db22fd03e8dc591b12169e99169dff | 51248d877bbc6e604e38aeaf776c2781cb4f0dbd, 28743571c17b58c21a7216fc9faaf8028df5869b, 264ccd7871915749bee55fe0c39467a7f08d5479, bb7caa63e1db22fd03e8dc591b12169e99169dff |
| Linux/Linuxgeneric | 6.11 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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().
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-72468 records a Unknown severity vulnerability in xprtrdma: Initialize re_id before removal registration. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3f4eb9ff923413cdb4c7e171c06d3564f6286712 <51248d877bbc6e604e38aeaf776c2781cb4f0dbd || >=3f4eb9ff923413cdb4c7e171c06d3564f6286712 <28743571c17b58c21a7216fc9faaf8028df5869b || >=3f4eb9ff923413cdb4c7e171c06d3564f6286712 <264ccd7871915749bee55fe0c39467a7f08d5479 || >=3f4eb9ff923413cdb4c7e171c06d3564f6286712 <bb7caa63e1db22fd03e8dc591b12169e99169dff | 51248d877bbc6e604e38aeaf776c2781cb4f0dbd, 28743571c17b58c21a7216fc9faaf8028df5869b, 264ccd7871915749bee55fe0c39467a7f08d5479, bb7caa63e1db22fd03e8dc591b12169e99169dff |
| Linux/Linuxgeneric | 6.11 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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().
Quoted source text, attributed separately from HOL analysis.