CVE-2026-72468
Last modified
CVE-2026-72468 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.20% chance of exploitation in the next 30 days.
Description
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().
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 3f4eb9ff923413cdb4c7e171c06d3564f6286712, < 51248d877bbc6e604e38aeaf776c2781cb4f0dbd; >= 3f4eb9ff923413cdb4c7e171c06d3564f6286712, < 28743571c17b58c21a7216fc9faaf8028df5869b; >= 3f4eb9ff923413cdb4c7e171c06d3564f6286712, < 264ccd7871915749bee55fe0c39467a7f08d5479; >= 3f4eb9ff923413cdb4c7e171c06d3564f6286712, < bb7caa63e1db22fd03e8dc591b12169e99169dff |
| Linux | Linux | 6.11 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-72468?
How severe is CVE-2026-72468?
How do I fix CVE-2026-72468?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-72462In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-72463In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-72464In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-72465In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-72466In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-72467In the Linux kernel, the following vulnerability has been re…
- CVE-2026-72469In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-7247A vulnerability has been found in D-Link DI-8100 16.07.26A1.…7.3
- CVE-2026-72470In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-72471In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-72472In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-72473In the Linux kernel, the following vulnerability has been re…9.8
Are you affected by CVE-2026-72468?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
