CVE-2026-64102
Linux kernel siw RDMA length underflow leads to kernel UAF, crash, and potential compromise
Is CVE-2026-64102 being exploited?
Not confirmed. CVE-2026-64102 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.50% probability of exploitation in the next 30 days.
How severe is CVE-2026-64102?
CVE-2026-64102 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-64102?
Yes. A fix has been recorded for CVE-2026-64102. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64102 affect?
CVE-2026-64102 affects Linux kernel (drivers/infiniband/sw/siw), Systems using soft-iWARP RDMA (iWARP over TCP). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64102?
Install kernel siw patch immediately; restrict iWARP/TCP from untrusted networks; reboot affected hosts
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote use-after-free via crafted iWARP FPDU enabling kernel memory disclosure, crash (DoS), and potential kernel compromise.
Immediate action required
- affected>= 8b6a361b8c482f22ac99c3273285ff16b23fba91 and < 683f7cfbf514193d63c0efa079f3352bde84c2e0
- affected>= 8b6a361b8c482f22ac99c3273285ff16b23fba91 and < 4a331582011d9e8089af8aa2a61ec6b4443bb245
- affected>= 8b6a361b8c482f22ac99c3273285ff16b23fba91 and < 33a8b5e971e294ec2a7b74211c545e09efd8e9ac
- affected>= 8b6a361b8c482f22ac99c3273285ff16b23fba91 and < 14553be882d9ce91749c9d64041de66e34ad8e70
- affected>= 8b6a361b8c482f22ac99c3273285ff16b23fba91 and < c7c0c0f4379dedec12d24dbb9dded5d2db7fd9f2
- affected>= 8b6a361b8c482f22ac99c3273285ff16b23fba91 and < 1012896f4225e8f801ff3c1648023845b66dfb11
- affected>= 8b6a361b8c482f22ac99c3273285ff16b23fba91 and < 775b4dc9618a99a1fa48b57554041a5dc17e1336
- affected>= 8b6a361b8c482f22ac99c3273285ff16b23fba91 and < 0ce1bc9e46ecabe84772bb561e373c0d9876d6f2
- affected5.3
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.