{"api_version":"1","generated_at":"2026-09-20T17:14:06+00:00","cve":"CVE-2026-80699","urls":{"html":"https://cve.report/CVE-2026-80699","api":"https://cve.report/api/cve/CVE-2026-80699.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-80699","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-80699"},"summary":{"title":"KVM: arm64: vgic: Avoid double-deactivate of IRQs in the nested context","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: arm64: vgic: Avoid double-deactivate of IRQs in the nested context\n\nIn the nested state, the physical interrupt has already been\ndeactivated through the HW bit in the LR. The extra deactivation\nwould be harmless but can hit an errata case on AmpereOne, so\navoid it here.\n\nOn AmpereOne, deactivating a physical interrupt through\nICC_DIR_EL1 or ICC_EOIR1_EL1 (depending on EOImode) which is not\nactive, but is the highest priority pending interrupt causes the\ncpu to lose the interrupt pending state and also prevents the\ndelivery of future interrupts.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-08-28 08:16:55","updated_at":"2026-08-28 08:16:55"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/f78f08b38a7f121c7d6b3e41002d9de7fd3c9189","name":"https://git.kernel.org/stable/c/f78f08b38a7f121c7d6b3e41002d9de7fd3c9189","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/8a570b19b4b16a8a3b5ffa2b332bd5613110b2d8","name":"https://git.kernel.org/stable/c/8a570b19b4b16a8a3b5ffa2b332bd5613110b2d8","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-80699","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80699","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6dd333c8942b2e5bb5927af843b56ec2857db7c7 f78f08b38a7f121c7d6b3e41002d9de7fd3c9189 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6dd333c8942b2e5bb5927af843b56ec2857db7c7 8a570b19b4b16a8a3b5ffa2b332bd5613110b2d8 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.19","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.19 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.8 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"80699","cve":"CVE-2026-80699","epss":"0.001550000","percentile":"0.049960000","score_date":"2026-08-30","updated_at":"2026-08-31 00:14:06"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["Documentation/arch/arm64/silicon-errata.rst","arch/arm64/kvm/vgic/vgic-v3.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"f78f08b38a7f121c7d6b3e41002d9de7fd3c9189","status":"affected","version":"6dd333c8942b2e5bb5927af843b56ec2857db7c7","versionType":"git"},{"lessThan":"8a570b19b4b16a8a3b5ffa2b332bd5613110b2d8","status":"affected","version":"6dd333c8942b2e5bb5927af843b56ec2857db7c7","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["Documentation/arch/arm64/silicon-errata.rst","arch/arm64/kvm/vgic/vgic-v3.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.19"},{"lessThan":"6.19","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"7.1.*","status":"unaffected","version":"7.1.8","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.8","versionStartIncluding":"6.19","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2","versionStartIncluding":"6.19","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: arm64: vgic: Avoid double-deactivate of IRQs in the nested context\n\nIn the nested state, the physical interrupt has already been\ndeactivated through the HW bit in the LR. The extra deactivation\nwould be harmless but can hit an errata case on AmpereOne, so\navoid it here.\n\nOn AmpereOne, deactivating a physical interrupt through\nICC_DIR_EL1 or ICC_EOIR1_EL1 (depending on EOImode) which is not\nactive, but is the highest priority pending interrupt causes the\ncpu to lose the interrupt pending state and also prevents the\ndelivery of future interrupts."}],"providerMetadata":{"dateUpdated":"2026-08-28T06:53:03.430Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/f78f08b38a7f121c7d6b3e41002d9de7fd3c9189"},{"url":"https://git.kernel.org/stable/c/8a570b19b4b16a8a3b5ffa2b332bd5613110b2d8"}],"title":"KVM: arm64: vgic: Avoid double-deactivate of IRQs in the nested context","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-80699","datePublished":"2026-08-28T06:53:03.430Z","dateReserved":"2026-08-26T14:34:25.786Z","dateUpdated":"2026-08-28T06:53:03.430Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-08-28 08:16:55","lastModifiedDate":"2026-08-28 08:16:55","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"80699","Ordinal":"1","Title":"KVM: arm64: vgic: Avoid double-deactivate of IRQs in the nested ","CVE":"CVE-2026-80699","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"80699","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: arm64: vgic: Avoid double-deactivate of IRQs in the nested context\n\nIn the nested state, the physical interrupt has already been\ndeactivated through the HW bit in the LR. The extra deactivation\nwould be harmless but can hit an errata case on AmpereOne, so\navoid it here.\n\nOn AmpereOne, deactivating a physical interrupt through\nICC_DIR_EL1 or ICC_EOIR1_EL1 (depending on EOImode) which is not\nactive, but is the highest priority pending interrupt causes the\ncpu to lose the interrupt pending state and also prevents the\ndelivery of future interrupts.","Type":"Description","Title":"KVM: arm64: vgic: Avoid double-deactivate of IRQs in the nested "}]}}}