{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72468 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72468 is a vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-72468 and fix it if it is affected.\n\nWhat it is: CVE-2026-72468 is a vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-72468 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-72468/ (Markdown: https://insights.sbomify.com/CVE-2026-72468/index.md)","id":"CVE-2026-72468","markdown":"https://insights.sbomify.com/CVE-2026-72468/index.md","name":"CVE-2026-72468","record":{"aliases":["BELL-CVE-2026-72468","DEBIAN-CVE-2026-72468","GHSA-5xgh-rmhf-2qq8","UBUNTU-CVE-2026-72468"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"high_privilege","summary":"A local administrator can trigger a kernel crash via a race condition in NFS/RDMA device removal, causing a denial of service.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nxprtrdma: Initialize re_id before removal registration\n\nrpcrdma_create_id() registers ep-\u003ere_rn with the rpcrdma ib_client\nbefore returning the new rdma_cm_id to rpcrdma_ep_create(). However\nrpcrdma_ep_create() currently stores that pointer in ep-\u003ere_id only\nafter rpcrdma_create_id() returns.\n\nA local administrator can race an NFS/RDMA mount against RDMA device\nremoval. If rpcrdma_remove_one() observes the just-registered\nnotification before rpcrdma_ep_create() assigns ep-\u003ere_id,\nrpcrdma_ep_removal_done() calls trace_xprtrdma_device_removal(NULL).\nThe tracepoint dereferences id-\u003edevice-\u003ename and copies\nid-\u003eroute.addr.dst_addr, so the callback can crash the kernel with a\nNULL pointer dereference.\n\nStore the rdma_cm_id in ep-\u003ere_id immediately before publishing\nep-\u003ere_rn. The existing error path still destroys the id directly if\nregistration fails; ep is then freed by the caller without using\nep-\u003ere_id. Remove the later duplicate assignment in rpcrdma_ep_create().","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"xprtrdma: Initialize re_id before removal registration","id":"CVE-2026-72468","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"xprtrdma: Fix ep kref imbalance on ADDR_CHANGE","id":"CVE-2026-72469"},"packages":[],"prev":{"headline":"xprtrdma: Check frwr_wp_create() during connect","id":"CVE-2026-72467"},"products":["Linux"],"published":"2026-08-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-17","vendors":["Linux"]},"summary":"A local administrator can trigger a kernel crash via a race condition in NFS/RDMA device removal, causing a denial of service.","url":"https://insights.sbomify.com/CVE-2026-72468/"}