Skip to content
Systems

CVE-2026-63860

8.4
High
EPSS 0.14%Patch availableJul 21, 2026

Linux kernel RDMA netlink string handling can cause kernel memory corruption and RCE.

common questions

Is CVE-2026-63860 being exploited?

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

How severe is CVE-2026-63860?

CVE-2026-63860 is rated High with a CVSS score of 8.4. 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-63860?

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

What does CVE-2026-63860 affect?

CVE-2026-63860 affects Linux kernel (rdma/core), Linux distributions using affected kernels. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-63860?

Apply vendor/kernel RDMA patch or update kernel ASAP

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

executive summary
technical analysis
affected
Linux kernel (rdma/core)Linux distributions using affected kernels
impact

Malformed RDMA netlink attributes lacking NUL can trigger kernel memory corruption, enabling kernel RCE or local privilege escalation.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= 30dc5e63d6a5ad24894b5512d10b228d73645a44 and < fcd07d3b8ee7a39b344d73aed69c1a68cd9eacdf
  • affected>= 30dc5e63d6a5ad24894b5512d10b228d73645a44 and < 87111356d58d86edb221ba144d261ed83a5b8bbe
  • affected>= 30dc5e63d6a5ad24894b5512d10b228d73645a44 and < abda65bdd13084c771842adaac1f652d0660dd82
  • affected>= 30dc5e63d6a5ad24894b5512d10b228d73645a44 and < 137b5918931d4d05aa8ea8d3adf67f7224eef63c
  • affected>= 30dc5e63d6a5ad24894b5512d10b228d73645a44 and < 5877c043398d5fa0e93919a3d837e5cd7a98a961
  • affected>= 30dc5e63d6a5ad24894b5512d10b228d73645a44 and < f2c7b39dde2e61df8157066969cc2a408cd3dcd9
  • affected>= 30dc5e63d6a5ad24894b5512d10b228d73645a44 and < c26a0052cceed4c4d380ee5808b699f937fb58d8
  • affected>= 30dc5e63d6a5ad24894b5512d10b228d73645a44 and < 6ed3d14fc45d3da6025e7fe4a6a09066856698e2
  • affected3.16
vendor says fixed in< 3.16, >= 5.10.258 and <= 5.10.*, >= 5.15.209 and <= 5.15.*, >= 6.1.175 and <= 6.1.*, >= 6.6.141 and <= 6.6.*, >= 6.12.91 and <= 6.12.*, >= 6.18.33 and <= 6.18.*, >= 7.0.10 and <= 7.0.*, >= 7.1 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