Skip to content
major vulnerability· requires attention

Affects Linux kernel KVM, a core virtualization component used across industries; potential host crash or VM escape.

Infrastructure

CVE-2026-46113

8.8
High
EPSS 0.15%Patch availableMay 30, 2026

KVM shadow paging UAF in Linux kernel; risk of host crash and VM escape.

common questions

Is CVE-2026-46113 being exploited?

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

How severe is CVE-2026-46113?

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

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

What does CVE-2026-46113 affect?

CVE-2026-46113 affects Linux kernel (KVM). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-46113?

Patch kernel to fixed version and reboot hosts

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

executive summary
technical analysis
affected
Linux kernel (KVM)
impact

KVM MMU shadow paging use-after-free may crash host or enable VM escape via guest page-table changes.

action required

Immediate action required

affected versions
Linux Linux
  • affected>= 6aa8b732ca01c3d7a54e93f4d701b8aabbe60fb7 and < e9d4ea13aa2b6400bb10ec64b370ba3dadcd22f0
  • affected>= 6aa8b732ca01c3d7a54e93f4d701b8aabbe60fb7 and < 488e386484ec8c0e558be6e156edf34ed9f4d5c8
  • affected>= 6aa8b732ca01c3d7a54e93f4d701b8aabbe60fb7 and < 06c19c967b845b63172601fe459667d973b7e6b7
  • affected>= 6aa8b732ca01c3d7a54e93f4d701b8aabbe60fb7 and < 738ec97b1855df6c08fe2369f798fa0b972e556b
  • affected>= 6aa8b732ca01c3d7a54e93f4d701b8aabbe60fb7 and < 14d1e55dfd2cf4711bff164a6aaaddb783552134
  • affected>= 6aa8b732ca01c3d7a54e93f4d701b8aabbe60fb7 and < 0cb2af2ea66ad8ff195c156ea690f11216285bdf
  • affected2.6.20
vendor says fixed in< 2.6.20, >= 6.1.175 and <= 6.1.*, >= 6.6.140 and <= 6.6.*, >= 6.12.88 and <= 6.12.*, >= 6.18.30 and <= 6.18.*, >= 7.0.7 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