KVM: arm64: vgic: Check the interrupt is still ours before migrating it
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel e363c0bc0226dc5ea5046a88e9a6864b82c45399, Kernel 0074b82cdfcb5fd13710a0ac308ade68ac6f6fbe, Kernel 0658b09cba7fe866c6cd70cd2dcdfdcabe80328f and 12 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=0919e84c0fc1fc73525fdcedefab89ea8460f697 <e363c0bc0226dc5ea5046a88e9a6864b82c45399, >=0919e84c0fc1fc73525fdcedefab89ea8460f697 <0074b82cdfcb5fd13710a0ac308ade68ac6f6fbe, >=0919e84c0fc1fc73525fdcedefab89ea8460f697 <0658b09cba7fe866c6cd70cd2dcdfdcabe80328f, >=0919e84c0fc1fc73525fdcedefab89ea8460f697 <3893e1fcf6f306b327a8358dcd1cbd077989a240, >=0919e84c0fc1fc73525fdcedefab89ea8460f697 <654be81c4c637af12709d47c7efc3302cd336513, >=0919e84c0fc1fc73525fdcedefab89ea8460f697 <79fdd2aa774e44847cd9bb7edc811e73e3dc7bfe, >=0919e84c0fc1fc73525fdcedefab89ea8460f697 <cb3efe1a354f1638726725c3ecee1ce8d1a7e2dc, >=0919e84c0fc1fc73525fdcedefab89ea8460f697 <da2d249a39a1881681c303ceea33f38ba1c5bbeb, =4.7 | e363c0bc0226dc5ea5046a88e9a6864b82c45399, 0074b82cdfcb5fd13710a0ac308ade68ac6f6fbe, 0658b09cba7fe866c6cd70cd2dcdfdcabe80328f, 3893e1fcf6f306b327a8358dcd1cbd077989a240, 654be81c4c637af12709d47c7efc3302cd336513, 79fdd2aa774e44847cd9bb7edc811e73e3dc7bfe, cb3efe1a354f1638726725c3ecee1ce8d1a7e2dc, da2d249a39a1881681c303ceea33f38ba1c5bbeb |
| linux-kernel: Kernel | >=5.11.0 <5.15.212, >=5.16.0 <6.1.178, >=6.13.0 <6.18.40, >=6.19.0 <7.1.5, >=6.2.0 <6.6.145, >=6.7.0 <6.12.97, >=4.7.0 <5.10.261 | 5.15.212, 6.1.178, 6.18.40, 7.1.5, 6.6.145, 6.12.97, 5.10.261 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket