CVE-2026-97611

Vulnérabilité élevée dans Linux (Linux)

CVSS 7.8 · Élevée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, 7.2.7, <035e9c3722067648a99010711d0ce81f42572ef4, 6.18.53, 0, <a0d18d21d48a551f82ee344e50efb8a682161489, 5.10.271, 6.6.158, <=5.10.*, <=6.6.*, 6.1.189, <4c98b492e9ed63f9ca3e23566d9a6a4f235944f4, <76678217cdabc41e3c74c23b45b62086ffb8fe7a, <=6.18.*, eac87c413bf9794c14d488998a5265ea5b32f04e, 5.9, 5.15.222, <5.9, <=7.2.*, <=*, <4016ead17acd75312c066ecd47c4b7f0a81ceaa2, <=5.15.*, <cd982e11684def5d4a9fcfd5354de09032828414, <017dbbf0d6c319a487f68e22f56d91fc787d5525, 6.12.111, <ba4ba11ed6eb8972c69070417fc27b48deb002e8, 7.3

Description

In the Linux kernel, the following vulnerability has been resolved: net: openvswitch: fix use-after-free of the flow table mask array tbl_mask_array_realloc() retires the old mask_array before it stops being reachable: old = ovsl_dereference(tbl->mask_array); if (old) { ... call_rcu(&old->rcu, mask_array_rcu_cb); } rcu_assign_pointer(tbl->mask_array, new); call_rcu() only waits for read-side critical sections already in flight. tbl->mask_array still points at old between the call_rcu() and the rcu_assign_pointer(), so a reader entering ovs_flow_tbl_lookup_stats() in that window picks up old in a fresh critical section that the pending grace period does not cover. tbl_mask_array_realloc() runs in process context under ovs_mutex, so the window is preemptible and can outlast the grace period. Then mask_array_rcu_cb() frees old before the swap runs: BUG: KASAN: slab-use-after-free in flow_lookup.constprop.0+0x2bf/0x2f0 Read of size 8 at addr ffff888020b3e018 by task poc/741 flow_lookup.constprop.0+0x2bf/0x2f0 ovs_flow_tbl_lookup_stats+0x4a3/0x5c0 ovs_dp_process_packet+0x19c/0x710 ovs_vport_receive+0x243/0x390 internal_dev_xmit+0x81/0x170 Freed by task 728: kfree+0x16a/0x4e0 rcu_core+0x853/0x1030 Publish the new array before retiring the old one. The kfree_rcu() that call_rcu() replaced ran after the swap.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, 7.2.7, <035e9c3722067648a99010711d0ce81f42572ef4, 6.18.53, 0, <a0d18d21d48a551f82ee344e50efb8a682161489, 5.10.271, 6.6.158, <=5.10.*, <=6.6.*, 6.1.189, <4c98b492e9ed63f9ca3e23566d9a6a4f235944f4, <76678217cdabc41e3c74c23b45b62086ffb8fe7a, <=6.18.*, eac87c413bf9794c14d488998a5265ea5b32f04e, 5.9, 5.15.222, <5.9, <=7.2.*, <=*, <4016ead17acd75312c066ecd47c4b7f0a81ceaa2, <=5.15.*, <cd982e11684def5d4a9fcfd5354de09032828414, <017dbbf0d6c319a487f68e22f56d91fc787d5525, 6.12.111, <ba4ba11ed6eb8972c69070417fc27b48deb002e8, 7.3) 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