KVM: arm64: vgic: Check the interrupt is still ours before migrating it
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: vgic: Check the interrupt is still ours before migrating it vgic_prune_ap_list() drops both ap_list_lock and irq_lock while migrating an interrupt to another vCPU. After reacquiring the locks it only checks that the affinity is unchanged (target_vcpu == vgic_target_oracle(irq)) before moving the interrupt, which assumes that an interrupt whose affinity is preserved is still queued on this vCPU's ap_list. That assumption no longer holds if the interrupt is taken off the ap_list while the locks are dropped. vgic_flush_pending_lpis() removes the interrupt from the list and sets irq->vcpu to NULL, but leaves enabled/pending/target_vcpu untouched. As the interrupt is still enabled and pending, vgic_target_oracle() returns the same target_vcpu, so the affinity check passes and list_del() is run a second time on an entry that has already been removed. Also check that the interrupt is still assigned to this vCPU (irq->vcpu == vcpu) before moving it.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 0919e84c0fc1fc73525fdcedefab89ea8460f697 · fixed in 3893e1fcf6f306b327a8358dcd1cbd077989a240; From 0919e84c0fc1fc73525fdcedefab89ea8460f697 · fixed in cb3efe1a354f1638726725c3ecee1ce8d1a7e2dc; From 0919e84c0fc1fc73525fdcedefab89ea8460f697 · fixed in da2d249a39a1881681c303ceea33f38ba1c5bbeb; From 0919e84c0fc1fc73525fdcedefab89ea8460f697 · fixed in 654be81c4c637af12709d47c7efc3302cd336513; From 0919e84c0fc1fc73525fdcedefab89ea8460f697 · fixed in e363c0bc0226dc5ea5046a88e9a6864b82c45399; From 0919e84c0fc1fc73525fdcedefab89ea8460f697 · fixed in 79fdd2aa774e44847cd9bb7edc811e73e3dc7bfe; From 0919e84c0fc1fc73525fdcedefab89ea8460f697 · fixed in 0658b09cba7fe866c6cd70cd2dcdfdcabe80328f; From 0919e84c0fc1fc73525fdcedefab89ea8460f697 · fixed in 0074b82cdfcb5fd13710a0ac308ade68ac6f6fbe
- Linux Linux
4.7
- KernelLinux
From 4.7.0 · fixed in 5.10.261; From 5.11.0 · fixed in 5.15.212; From 5.16.0 · fixed in 6.1.178; From 6.2.0 · fixed in 6.6.145; From 6.7.0 · fixed in 6.12.97; From 6.13.0 · fixed in 6.18.40; From 6.19.0 · fixed in 7.1.5
References 8
git.kernel.org
- stable/c/3893e1fcf6f306b327a8358dcd1cbd077989a240
- stable/c/cb3efe1a354f1638726725c3ecee1ce8d1a7e2dc
- stable/c/da2d249a39a1881681c303ceea33f38ba1c5bbeb
- stable/c/654be81c4c637af12709d47c7efc3302cd336513
- stable/c/e363c0bc0226dc5ea5046a88e9a6864b82c45399
- stable/c/79fdd2aa774e44847cd9bb7edc811e73e3dc7bfe
- stable/c/0658b09cba7fe866c6cd70cd2dcdfdcabe80328f
- stable/c/0074b82cdfcb5fd13710a0ac308ade68ac6f6fbe