Linux kernel vulnerability in svc_rdma affects core server OS; can crash kernels on systems using RDMA/NFS and impacts broad infrastructure.
CVE-2026-89532
Linux kernel svc_rdma OOB read can crash kernel via crafted RDMA/NFS chunks
Is CVE-2026-89532 being exploited?
Not confirmed. CVE-2026-89532 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.51% probability of exploitation in the next 30 days.
How severe is CVE-2026-89532?
CVE-2026-89532 is rated Critical with a CVSS score of 9.1. 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-89532?
Yes. A fix has been recorded for CVE-2026-89532. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-89532 affect?
CVE-2026-89532 affects Linux kernel (net/sunrpc xprtrdma svc_rdma), NFS over RDMA servers, Distributions with RDMA/SUNRPC enabled. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-89532?
Apply the upstream/vendor kernel patch or updated distro kernel and restart RDMA/NFS services.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote out-of-bounds read triggers kernel general protection fault -> remote kernel crash/denial-of-service on affected servers.
Immediate action required
- affected>= 78147ca8b4a9b6cf0e597ddd6bf17959e08376c2 and < 1e2e3481e39103a386b86be1c33eaef97cbdf16e
- affected>= 78147ca8b4a9b6cf0e597ddd6bf17959e08376c2 and < 3a78b841879c2a3243f74edc514236fb2907167f
- affected>= 78147ca8b4a9b6cf0e597ddd6bf17959e08376c2 and < 06d0390c37fa6714624af771bd72bbf1a7ed9bb1
- affected>= 78147ca8b4a9b6cf0e597ddd6bf17959e08376c2 and < 9c5a03c3dc505c0295339b0a1b9e4fe36447e482
- affected>= 78147ca8b4a9b6cf0e597ddd6bf17959e08376c2 and < a1c954ca4977a4e6ec73ef92fe48073ec54f9fc8
- affected>= 78147ca8b4a9b6cf0e597ddd6bf17959e08376c2 and < 6d33a7e6bf6c6b293a266a617201285a1ad32c56
- affected>= 78147ca8b4a9b6cf0e597ddd6bf17959e08376c2 and < b7713a784c59515d0aba558c8f5df6a0164dd3a9
- affected5.11
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.