Skip to content
major vulnerability· requires attention

Kernel-level overflow in svcrdma (RPC-over-RDMA) impacts Linux NFS/RDMA servers; high-severity, widespread kernel bug that can disrupt infrastructure and is newsworthy.

Systems

CVE-2026-89530

9.8
Critical
EPSS 0.46%Patch availableSep 13, 2026

Linux kernel svcrdma overflow allowing remote kernel memory corruption

common questions

Is CVE-2026-89530 being exploited?

Not confirmed. CVE-2026-89530 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.46% probability of exploitation in the next 30 days.

How severe is CVE-2026-89530?

CVE-2026-89530 is rated Critical with a CVSS score of 9.8. 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-89530?

Yes. A fix has been recorded for CVE-2026-89530. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-89530 affect?

CVE-2026-89530 affects Linux kernel (svcrdma/RPC-over-RDMA), NFS servers using RDMA, Linux distributions shipping affected kernel versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-89530?

Apply the kernel stable patch or distro kernel update immediately and reboot hosts.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (svcrdma/RPC-over-RDMA)NFS servers using RDMALinux distributions shipping affected kernel versions
impact

Remote kernel memory corruption via crafted RPC-over-RDMA reply; can cause panics, data corruption, or lead to remote code execution.

action required

Immediate action required

affected versions
Linux Linux
  • affected>= e248aa7be86e8179f20ac0931774ecd746f3f5bf and < fcd91b9957462d398792201c239dffaeff1cc8b2
  • affected>= e248aa7be86e8179f20ac0931774ecd746f3f5bf and < 1949dd1576f7a8aa161b1330c6125df9d53046d5
  • affected>= e248aa7be86e8179f20ac0931774ecd746f3f5bf and < 8ec60eb51fae37cd3d334ff26e4a7d6fb21ff7cf
  • affected>= e248aa7be86e8179f20ac0931774ecd746f3f5bf and < 0fbe20dfe74b783d255bf389a6ea77aa25dc7860
  • affected9b65b18f817d9ada2bf67351f24bdcce6789a0bb
  • affectedd564356e1919d1178568c19af410cfc1a9076663
  • affected>= 4.19.22 and < 4.20
  • affected>= 4.20.9 and < 4.21
  • affected5.0
vendor says fixed in< 5.0, >= 6.12.109 and <= 6.12.*, >= 6.18.50 and <= 6.18.*, >= 7.2.4 and <= 7.2.*, >= 7.3-rc1 and <= *

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free