Improper Enforcement of Behavioral Workflow The advisory has been revoked - it doesn't affect any version of package kernel-rt-debug-kvm (opens in a new tab)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-CENTOS10-KERNELRTDEBUGKVM-16930747
- published28 May 2026
- disclosed27 May 2026
Introduced: 27 May 2026
CVE-2026-46059 (opens in a new tab)Amendment
The Centos security team deemed this advisory irrelevant for Centos:10.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel-rt-debug-kvm package and not the kernel-rt-debug-kvm package as distributed by Centos.
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]
References
- https://bugzilla.redhat.com/show_bug.cgi?id=2481944
- https://access.redhat.com/security/cve/CVE-2026-46059
- https://git.kernel.org/stable/c/3428ed1529a1af4cce5aff6c5bd2fcc39ad726bb
- https://git.kernel.org/stable/c/69fe1411a5ce678b4da6489b5d2282b4e1d13acf
- https://git.kernel.org/stable/c/8d397582f6b5e9fbcf09781c7c934b4910e94a50
- https://git.kernel.org/stable/c/b1a45e8a59bcf1f1ec0da6d4e42190b4211c67fc
- https://git.kernel.org/stable/c/f9197a9dd1408e203147326139122f9c5312ce9c
- https://git.kernel.org/stable/c/98717fb482fa269db491f7c84aec777d3aeb2cd1