llamaCVEVulnerability Intelligence
/
Linux kernel

CVE-2026-99312

Linux kernel stale MMU context after INIT in KVM nested SVM

In nested SVM setups, the first-level hypervisor can keep running with a stale MMU context after an INIT event.

Parche disponible
Descargar PNG JSON
CVSS
—
N/D
Fuente: —
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche2 versiones5.16 · 6.1
Exposición20 hDesde la divulgación, 18 nov 2026, 3:42 a. m.
Detección13 minDesde la divulgación hasta su ingreso al índice
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Explotación
Remediación
Monitoreo
Detectada
Fuente: NIST NVD +2
03:42 a. m.
04:27 a. m.
11:36 p. m.
03:42 a. m.
08:40 a. m.
01:39 p. m.
06:37 p. m.
11:36 p. m.
FechaFaseEventoDetalle
Divulgación Publicada CVE-2026-99312 divulgada
Monitoreo Detectada Ingresó al índice
Monitoreo Fuente: NIST NVD Registro visto por primera vez en NIST NVD
Monitoreo Fuente: ENISA EUVD Registro visto por primera vez en ENISA EUVD
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Resumen generado por IA · CC-BY 4.0 · 18 nov 2026

The Linux kernel's KVM x86 code does not always reset the MMU context when emulating an INIT event, so the first-level guest hypervisor (L1) can keep running with a stale MMU context. The flaw only affects nested SVM setups.

Descripción original del registro (Linux)

In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Unconditionally reset MMU context when emulating INIT Force an MMU reset when emulating an INIT even if paging was already disabled, as the MMU page role includes guest_mode (L2), i.e. an INIT while L2 is running with CR0.PG=0 will result in KVM running L1 with a stale MMU context. Alternatively, the reset could be scoped strictly to paging being enabled or L2 being active, but SMM is also encoded in the page role. Even though it _should_ be impossible for the vCPU to be INIT'd while SMM is active, there's zero value in not handling SMM. At that point, the only scenario where KVM _doesn't_ need to reset the MMU context is on an INIT with the vCPU running in Real Mode or Unpaged Protect Mode, and while INIT in those modes is somewhat common, it's far from a hot path and re-initializing the MMU is not expensive, especially when the role isn't changing (KVM elides most of the re-configuration in that case). Note, like the Fixes commit, this bug only affects nested SVM as INIT is an unconditional intercept on VMX, i.e. it's impossible to emulate INIT while L2 is active. Temporarily keep the guest TLB flush when CR0.PG is being cleared even though it is fully redundant with the flush that is emitted on all INIT events (KVM itself only does RESET when a vCPU is being created, i.e. when CR0.PG must be '0').

Versiones

Rangos afectados

Afectada Corregida
Linux≥ 5.15.81 < 5.16
Linux≥ 6.0.11 < 6.1
5.15.81
5.16
6.0.11
6.1
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
Linux
Corregida 5.16, 6.1 — —
Versiones corregidas5.166.1
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Otrahttps://git.kernel.org/stable/c/f55a3e4e08dc004b4bab7c1e9323d7e7e96e266a
Otrahttps://git.kernel.org/stable/c/24f644ea26c2ebb7b14c3baa2aa92d37fde3095f
Otrahttps://git.kernel.org/stable/c/d47bae9eb33b3ca0843a0954b7d0cafb354c99b0
Otrahttps://git.kernel.org/stable/c/c7c288d178cb0b78d3464a616b16b1aa0b316049

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.