CVE-2026-72289

Vulnérabilité critique dans Linux (Linux)

CVSS 9.3 · Critique
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, 7.1.5, 6.18.40, <=6.12.*, 0, <=7.1.*, <e363c0bc0226dc5ea5046a88e9a6864b82c45399, <654be81c4c637af12709d47c7efc3302cd336513, 6.1.178, <=5.10.*, <=6.6.*, 6.12.97, <3893e1fcf6f306b327a8358dcd1cbd077989a240, 4.7, <=6.18.*, 5.15.212, 6.6.145, 5.10.261, 0919e84c0fc1fc73525fdcedefab89ea8460f697, <cb3efe1a354f1638726725c3ecee1ce8d1a7e2dc, <da2d249a39a1881681c303ceea33f38ba1c5bbeb, <=*, <=5.15.*, <0658b09cba7fe866c6cd70cd2dcdfdcabe80328f, <4.7, 7.2, <0074b82cdfcb5fd13710a0ac308ade68ac6f6fbe, <79fdd2aa774e44847cd9bb7edc811e73e3dc7bfe

Description

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.

Gravité et risque d'exploitation

CVE-2026-72289 obtient un score CVSS de 9.3/10, soit une gravité critique. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.18 %, ce qui la place devant 7.6 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, 7.1.5, 6.18.40, <=6.12.*, 0, <=7.1.*, <e363c0bc0226dc5ea5046a88e9a6864b82c45399, <654be81c4c637af12709d47c7efc3302cd336513, 6.1.178, <=5.10.*, <=6.6.*, 6.12.97, <3893e1fcf6f306b327a8358dcd1cbd077989a240, 4.7, <=6.18.*, 5.15.212, 6.6.145, 5.10.261, 0919e84c0fc1fc73525fdcedefab89ea8460f697, <cb3efe1a354f1638726725c3ecee1ce8d1a7e2dc, <da2d249a39a1881681c303ceea33f38ba1c5bbeb, <=*, <=5.15.*, <0658b09cba7fe866c6cd70cd2dcdfdcabe80328f, <4.7, 7.2, <0074b82cdfcb5fd13710a0ac308ade68ac6f6fbe, <79fdd2aa774e44847cd9bb7edc811e73e3dc7bfe) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références