CVE-2026-46059

In the Linux kernel, the following vulnerability has been resolved: KVM: nSVM: Always use NextRIP as vmcb02's NextRIP after first L2 VMRUN For guests with NRIPS disabled, L1 does not provide NextRIP when running an L2 with an injected soft interrupt, instead it advances the current RIP before running it. KVM uses the current RIP as the NextRIP in vmcb02 to emulate a CPU without NRIPS. However, after L2 runs the first time, NextRIP will be updated by the CPU and/or KVM, and the current RIP is no longer the correct value to use in vmcb02. Hence, after save/restore, use the current RIP if and only if a nested run is pending, otherwise use NextRIP. Give soft_int_next_rip the same treatment, as it's the same logic, just for a narrower use case. [sean: give soft_int_next_rip the same treatment]

Package Linux Kernel
Published 2026-05-27
Last modified 2026-05-27
Patch available
Yes

Affected versions

Linux kernel versions 5.8 and later are affected. Fixed in 6.18.27, 7.0.4, 7.1-rc1 and their respective stable series.

Affected from
≥ 5.8
Fixed in
✓ 6.18.27 6.18.x ✓ 7.0.4 7.0.x ✓ 7.1-rc1

References

The following references provide additional information about CVE-2026-46059 including vendor advisories, patch commits, exploit details, and third-party analysis. Links are sourced from the NIST NVD database.

Frequently asked questions

  • What is CVE-2026-46059?

    CVE-2026-46059 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 5.8 onward and has been patched in 6.18.27, 7.0.4 and 7.1-rc1. CVE-2026-46059 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

  • Is there a patch available for CVE-2026-46059?

    Yes — CVE-2026-46059 has been patched. Fixed versions include 6.18.27, 7.0.4 and 7.1-rc1. If you are running Linux kernel 5.8 or later up to the fix versions, apply the relevant patch for your kernel branch.

  • Is CVE-2026-46059 actively exploited?

    No — CVE-2026-46059 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.