CVE-2026-89916
In the Linux kernel, the following vulnerability has been resolved:
KVM: arm64: Make VNCR invalidation participate in MMU invalidation retry
A VNCR TLB invalidation can occur on one vcpu while another vcpu is faulting in this same page. Without correctly handling this, we can end up with the following scenario:
- vcpu A walks the PTs to translate VNCR - before vcpu A is able to grab the MMU lock to insert the TLB, vcpu B updates the S1 PTs with an invalid entry, and issues a TLBI S1E2 for this VA - vcpu A inserts the TLB for something that is now invalid
This isn't a new problem, and we manage S2 by having the MMU notifier to bump up mmu_invalidate_seq on invalidation so that the fault can be replayed.
Leer descripción completaMostrar menos
We can perform something similar here, and extend invalidate_vncr_va() to update the same counter, clearly indicating that the context has changed under our feet. This is safe as the invalidation always happen while holding the MMU lock for write, and that we sample the sequence number before walking S1.
CVSS
- Versión: 3.1
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
- Puntuación base: 9.3
Probabilidad de explotación (EPSS)
- Probabilidad de explotación en los próximos 30 días: 0.19%
- Percentil entre todas las CVEs puntuadas: 8
- Fecha de la puntuación: 5/10/2026
EPSS (Exploit Prediction Scoring System, de FIRST) estima la probabilidad de que una vulnerabilidad sea explotada en 30 días. Complementa a CVSS (impacto) y a CISA KEV (explotación confirmada).
🎯 Técnicas ATT&CK
Cómo se explota esta vulnerabilidad y qué consigue el atacante, en el lenguaje de MITRE ATT&CK.
- Explotación
T1068Exploitation for Privilege Escalationprivilege escalation85 % - Impacto principal
T1499.004Application or System Exploitationimpact75 %
Vulnerabilidad local del kernel (AV:L, PR:N) en KVM arm64 causando race condition que afecta sincronización MMU. Sin privilegios previos, permite DoS por corrupción de memoria virtual y daño de datos del hipervisor.
Inferido por nuestro agente de análisis a partir de la descripción oficial, el vector CVSS y la CWE, y comprobado por un supervisor. Puede contener errores.
🛡️ Mitigaciones ATT&CK que cubren estas técnicas
Tecnologías afectadas (1)
⚠ Inferidas por IA a partir de la descripción — NVD aún no ha analizado esta CVE; no son CPE verificados.
Referencias
JSON original (NVD)
Mostrar
{
"id": "CVE-2026-89916",
"cveTags": [],
"metrics": {
"cvssMetricV31": [
{
"type": "Secondary",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"cvssData": {
"scope": "CHANGED",
"version": "3.1",
"baseScore": 9.3,
"attackVector": "LOCAL",
"baseSeverity": "CRITICAL",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H",
"integrityImpact": "HIGH",
"userInteraction": "NONE",
"attackComplexity": "LOW",
"availabilityImpact": "HIGH",
"privilegesRequired": "NONE",
"confidentialityImpact": "HIGH"
},
"impactScore": 6,
"exploitabilityScore": 2.5
}
]
},
"affected": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"affectedData": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929",
"lessThan": "d8580e7aa189b0c6c5bb4d94b8352728a7c35bbd",
"versionType": "git"
},
{
"status": "affected",
"version": "4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929",
"lessThan": "11ee3faab4f1755d126bead9f882e75a7a677860",
"versionType": "git"
},
{
"status": "affected",
"version": "4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929",
"lessThan": "2b7324f3a0c1072b9d578b8d42f199506753f26e",
"versionType": "git"
}
],
"programFiles": [
"arch/arm64/kvm/nested.c"
],
"defaultStatus": "unaffected"
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "6.16"
},
{
"status": "unaffected",
"version": "0",
"lessThan": "6.16",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "6.18.51",
"versionType": "semver",
"lessThanOrEqual": "6.18.*"
},
{
"status": "unaffected",
"version": "7.2.5",
"versionType": "semver",
"lessThanOrEqual": "7.2.*"
},
{
"status": "unaffected",
"version": "7.3-rc1",
"versionType": "original_commit_for_fix",
"lessThanOrEqual": "*"
}
],
"programFiles": [
"arch/arm64/kvm/nested.c"
],
"defaultStatus": "affected"
}
]
}
],
"published": "2026-09-16T11:17:00.657",
"references": [
{
"url": "https://git.kernel.org/stable/c/11ee3faab4f1755d126bead9f882e75a7a677860",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/2b7324f3a0c1072b9d578b8d42f199506753f26e",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/d8580e7aa189b0c6c5bb4d94b8352728a7c35bbd",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"vulnStatus": "Received",
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: arm64: Make VNCR invalidation participate in MMU invalidation retry\n\nA VNCR TLB invalidation can occur on one vcpu while another vcpu is\nfaulting in this same page. Without correctly handling this, we can\nend up with the following scenario:\n\n- vcpu A walks the PTs to translate VNCR\n- before vcpu A is able to grab the MMU lock to insert the TLB,\n vcpu B updates the S1 PTs with an invalid entry, and issues\n a TLBI S1E2 for this VA\n- vcpu A inserts the TLB for something that is now invalid\n\nThis isn't a new problem, and we manage S2 by having the MMU notifier\nto bump up mmu_invalidate_seq on invalidation so that the fault can be\nreplayed.\n\nWe can perform something similar here, and extend invalidate_vncr_va() to\nupdate the same counter, clearly indicating that the context has\nchanged under our feet. This is safe as the invalidation always happen\nwhile holding the MMU lock for write, and that we sample the sequence\nnumber before walking S1."
}
],
"lastModified": "2026-09-16T15:18:17.883",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}