Skip to content
Systems

CVE-2026-64552

8.4
High
EPSS 0.14%Patch availableJul 30, 2026

Virtio-net length check flaw allows guest kernel memory corruption.

common questions

Is CVE-2026-64552 being exploited?

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

CVE-2026-64552 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-64552?

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

What does CVE-2026-64552 affect?

CVE-2026-64552 affects Linux kernel (virtio-net), Virtualized guests using virtio-net, Environments with untrusted virtio backends. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-64552?

Install vendor Linux kernel security update; restrict or isolate untrusted virtio backends.

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

executive summary
technical analysis
affected
Linux kernel (virtio-net)Virtualized guests using virtio-netEnvironments with untrusted virtio backends
impact

Malicious virtio backend can trigger an OOB write in guest kernel, causing crashes or potential arbitrary kernel memory corruption/RCE.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= 82f9028e83944a9eee5229cbc6fee9be1de8a62d and < f9451d0fd5ba635dcabb49bfe456a6db734a8986
  • affected>= 946dec89c41726b94d31147ec528b96af0be1b5a and < 38e94d63e29f4a5c6eae87ee2c02101aaa321502
  • affected>= 82fe78065450d2d07f36a22e2b6b44955cf5ca5b and < fbeb65154583879d556ea94cb2f15888e9470f3d
  • affected>= 0c716703965ffc5ef4311b65cb5d84a703784717 and < c7fc9adf4e006155f7f2aeda052fbcde25cdcc49
  • affected>= 0c716703965ffc5ef4311b65cb5d84a703784717 and < e6b8463b7d791f3886d7584259d6e9f06a69f12e
  • affected>= 0c716703965ffc5ef4311b65cb5d84a703784717 and < 9e5ad06ea826322ce8c58b4a68442a96f600c3c4
  • affected3e9d89f2ecd3636bd4cbdfd0b2dfdaf58f9882e2
  • affected>= 6.1.159 and < 6.1.178
  • affected>= 6.6.117 and < 6.6.145
  • affected>= 6.12.58 and < 6.12.97
  • affected>= 6.17.8 and < 6.18
  • affected6.18
vendor says fixed in< 6.18, >= 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.5 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