Skip to content
Systems

CVE-2026-64438

HIGH
High
EPSS 0.14%Patch availableJul 27, 2026

intel_qat driver use-after-free in SR-IOV teardown causing kernel crash or memory corruption

common questions

Is CVE-2026-64438 being exploited?

Not confirmed. CVE-2026-64438 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-64438?

CVE-2026-64438 is rated High. 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-64438?

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

What does CVE-2026-64438 affect?

CVE-2026-64438 affects Linux kernel (intel_qat driver), Systems using Intel QuickAssist Technology (QAT) with SR-IOV, Data center appliances using QAT VF/PF. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-64438?

Install vendor kernel/driver update and reboot affected hosts immediately

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

executive summary
technical analysis
affected
Linux kernel (intel_qat driver)Systems using Intel QuickAssist Technology (QAT) with SR-IOVData center appliances using QAT VF/PF
impact

Use-after-free in kernel driver can cause kernel memory corruption, crashes (DoS) and may enable privilege escalation or host compromise on affected systems.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= ed8ccaef52fa03fb03cff45b380f72c9f869f273 and < 218c2836b3987f3fa1d9eac505462cded0821e4c
  • affected>= ed8ccaef52fa03fb03cff45b380f72c9f869f273 and < 446b4d77599cf1a168573f7fb32a4a6aa4f09219
  • affected>= ed8ccaef52fa03fb03cff45b380f72c9f869f273 and < 5d916c1eae1933511a69bffe243b4ee5d7da399c
  • affected>= ed8ccaef52fa03fb03cff45b380f72c9f869f273 and < f344a369d0380d54c8d6c8d24734a78dd5a89817
  • affected>= ed8ccaef52fa03fb03cff45b380f72c9f869f273 and < 51144032248cc4ea22917370565650670b8b4e9b
  • affected>= ed8ccaef52fa03fb03cff45b380f72c9f869f273 and < 49cd5ac6de8de39a14ead609bb552d372d5602cd
  • affected>= ed8ccaef52fa03fb03cff45b380f72c9f869f273 and < 6e92b28cd74fa433658efeadf21b9d4b01023d7d
  • affected>= ed8ccaef52fa03fb03cff45b380f72c9f869f273 and < 277281c10c63791067d24d421f7c43a15faa9096
  • affected4.3
vendor says fixed in< 4.3, >= 5.10.261 and <= 5.10.*, >= 5.15.212 and <= 5.15.*, >= 6.1.178 and <= 6.1.*, >= 6.6.145 and <= 6.6.*, >= 6.12.97 and <= 6.12.*, >= 6.18.40 and <= 6.18.*, >= 7.1.4 and <= 7.1.*, >= 7.2 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