CVE-2026-72469
Linux kernel rpcrdma use-after-free on ADDR_CHANGE allows kernel crash or possible RCE.
Is CVE-2026-72469 being exploited?
Not confirmed. CVE-2026-72469 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.32% probability of exploitation in the next 30 days.
How severe is CVE-2026-72469?
CVE-2026-72469 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-72469?
Yes. A fix has been recorded for CVE-2026-72469. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-72469 affect?
CVE-2026-72469 affects Linux kernel (rpcrdma/xprtrdma), RDMA-enabled servers, Kernels with RDMA/RPC modules. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-72469?
Apply vendor kernel updates with the rpcrdma fix; restrict RDMA access or unload rpcrdma until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote use-after-free in rpcrdma can crash the kernel or enable code execution in kernel context via crafted RDMA events.
Patch when possible
- affected>= 2acc5cae292355f5f18ad377a2a966e7f03c8fec and < cfd1bab66b042da7a778786685125656c695931b
- affected>= 2acc5cae292355f5f18ad377a2a966e7f03c8fec and < d0479c2b12974aa188b10d221a5770126b118b6d
- affected>= 2acc5cae292355f5f18ad377a2a966e7f03c8fec and < ffc07790539736a5d029f6a3c966b46c529f93a8
- affected>= 2acc5cae292355f5f18ad377a2a966e7f03c8fec and < af9b65b29af341932625c4283dc7a23cdb62688a
- affected2fcbf07a4f23174a45e015b62a8e42ddbc2e53ef
- affected>= 5.7.9 and < 5.8
- affected5.8
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.