CVE-2026-72284KVM: x86: Ignore pending PV EOI if the vCPU has since disabled PV EOIs
- 7.1HighCVSS base score
- 0.19%Exploitation in 30 daysEPSS · top 91% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Ignore pending PV EOI if the vCPU has since disabled PV EOIs Ignore KVM's internal "service pending PV EOI" request if the vCPU has disabled PV EOIs since the request was made. Asserting that PV EOIs are enabled can fail if reading guest memory in pv_eoi_get_user() fails, i.e. if pv_eoi_test_and_clr_pending() bails early, *and* the vCPU also disables PV EOIs. kernel BUG at arch/x86/kvm/lapic.c:3338! Oops: invalid opcode: 0000 [#1] SMP CPU: 4 UID: 1000 PID: 890 Comm: pv_eoi_test Not tainted 7.0.0-d585aa5894d8-vm #337 PREEMPT Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015 RIP: 0010:kvm_lapic_sync_from_vapic+0x12b/0x140 [kvm] Call Trace: <TASK> kvm_arch_vcpu_ioctl_run+0x1075/0x1c30 [kvm] kvm_vcpu_ioctl+0x2d5/0x980 [kvm] __x64_sys_ioctl+0x8a/0xd0 do_syscall_64+0xb5/0xb40 entry_SYSCALL_64_after_hwframe+0x4b/0x53 </TASK> Modules linked in: kvm_intel kvm irqbypass ---[ end trace 0000000000000000 ]---
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 2 months later
· 2 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.1 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H |
| NVDNVD · Received | 3.1 | High7.1 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.19% · top 91% of all CVEs (17 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.1.
Affected products
- affected ae7a2a3fb6f8b784c2752863f4f1f20c656f76fb – < 038b9ce6fafda1babd1e33d52cbc6039747a6d87
- affected ae7a2a3fb6f8b784c2752863f4f1f20c656f76fb – < 8e9f7a95279bf608cf4c331ed89612e28c04564f
- affected ae7a2a3fb6f8b784c2752863f4f1f20c656f76fb – < ebd7845ca0471d251a1cb48d84eb165aff5b7123
- affected ae7a2a3fb6f8b784c2752863f4f1f20c656f76fb – < 97542f15dc4cf6cd3fdc035e482dca54246ddf48
- affected ae7a2a3fb6f8b784c2752863f4f1f20c656f76fb – < 32bdca80aa81c2cb906f50a88b220ce1ecdc5e6e
- affected ae7a2a3fb6f8b784c2752863f4f1f20c656f76fb – < 9285e4070df2c40585c3d7ec9571faa7a2b97e17
- affected 3.6
- unaffected < 3.6
- unaffected 6.1.178 – ≤ 6.1.*
- unaffected 6.6.145 – ≤ 6.6.*
- unaffected 6.12.97 – ≤ 6.12.*
- unaffected 6.18.40 – ≤ 6.18.*
- unaffected 7.1.5 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References6
- https://git.kernel.org/stable/c/038b9ce6fafda1babd1e33d52cbc6039747a6d87 (opens in a new tab)
- https://git.kernel.org/stable/c/8e9f7a95279bf608cf4c331ed89612e28c04564f (opens in a new tab)
- https://git.kernel.org/stable/c/ebd7845ca0471d251a1cb48d84eb165aff5b7123 (opens in a new tab)
- https://git.kernel.org/stable/c/97542f15dc4cf6cd3fdc035e482dca54246ddf48 (opens in a new tab)
- https://git.kernel.org/stable/c/32bdca80aa81c2cb906f50a88b220ce1ecdc5e6e (opens in a new tab)
- https://git.kernel.org/stable/c/9285e4070df2c40585c3d7ec9571faa7a2b97e17 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-59183 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-72284)Record last updated .