CVE-2026-64280
Integer-truncation in Linux dfl-afu ioctl allows kernel memory corruption via oversized DMA length
Is CVE-2026-64280 being exploited?
Not confirmed. CVE-2026-64280 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.17% probability of exploitation in the next 30 days.
How severe is CVE-2026-64280?
CVE-2026-64280 is rated High with a CVSS score of 8.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-64280?
Yes. A fix has been recorded for CVE-2026-64280. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64280 affect?
CVE-2026-64280 affects Linux kernel (dfl-afu driver), FPGA platforms using DFL AFU, Systems exposing DFL_FPGA_PORT_DMA_MAP ioctl. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64280?
Install the kernel patch that validates DMA map length; restrict access to FPGA device nodes until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local attacker can pass a large DMA length to trigger integer truncation, causing kernel memory corruption leading to privilege escalation or DoS.
Patch when possible
- affected>= fa8dda1edef9ebc3af467c644c5533ac97171e12 and < 5352d488ce4ae5e8c68c080ad4c3a5f084ad5fbc
- affected>= fa8dda1edef9ebc3af467c644c5533ac97171e12 and < d7e787eee2ea619b6dbb98890472ee73daf2e7fd
- affected>= fa8dda1edef9ebc3af467c644c5533ac97171e12 and < a6a3884ff500f04f3088d6d09eec803cd35331a2
- affected>= fa8dda1edef9ebc3af467c644c5533ac97171e12 and < 16381bda90b261a656ded0568630c1b857b2ebc8
- affected>= fa8dda1edef9ebc3af467c644c5533ac97171e12 and < b50e6cd2395cde615f59b624819998d28c0668d6
- affected>= fa8dda1edef9ebc3af467c644c5533ac97171e12 and < 59070040fd12e0b78d7b4d341d9f9a183237c5ff
- affected>= fa8dda1edef9ebc3af467c644c5533ac97171e12 and < fb2c0eab51ae5b02d2bae7d67c2cfbec39b57231
- affected>= fa8dda1edef9ebc3af467c644c5533ac97171e12 and < fc3b071a7c8dc0f5d56defddf6e6fd5aaa3e1e27
- affected4.19
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.