CVE-2026-46059

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