Heimdall Security Logo

CVE-2026-64095

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

CVSS 7.1 · Élevée
EPSS 0.3%
Linux•Linux•Versions : <=6.1.*, <=7.0.*, <=6.12.*, 6.12.93, 0, <1f013bc94154f2e78e97d0296175664224c796e0, <461f1e3dfb888701895b766446c55db2b10db705, 6.1.176, 5.15.210, 3.5, <=5.10.*, <=6.6.*, <5328b95960774f2e189f22485616bc7b8eb2f7e3, 6.18.34, <3.5, 7.1, <=6.18.*, 7.0.11, <a9393751ecf7e9096f93cb6eed02db4f79125765, <=*, <65497ad155a3246df177b5ef662cd6e5a32cb470, <=5.15.*, 6.6.143, 23721387c409087fd3b97e274f34d3ddc0970b74, <45384612f29692fbf0c770200361a7acff90125c, <83ab69bd12b80f6ea169c8bea6977701b53a043d, <8ff9c59d1b7b48c2596878341a5310f32895d52b, 5.10.259

Description

In the Linux kernel, the following vulnerability has been resolved: batman-adv: bla: avoid double decrement of bla.num_requests The bla.num_requests is increased when no request_sent was in progress. And it is decremented in various places (announcement was received, backbone is purged, periodic work). But the check if the request_sent is actually set to a specific state and the atomic_dec/_inc are not safe because they are not atomic (TOCTOU) and multiple such code portions can run concurrently. At the same time, it is necessary to modify request_sent (state) and bla.num_requests atomically. Otherwise batadv_bla_send_request() might set request_sent to 1 and is interrupted. batadv_handle_announce() can then set request_sent back to 0 and decrement num_requests before batadv_bla_send_request() incremented it. The two operations must therefore be locked. And since state (request_sent) and wait_periods are only accessed inside this lock, they can be converted to simpler datatypes. And to avoid that the bla.num_requests is touched by a parallel running context with a valid backbone_gw reference after batadv_bla_purge_backbone_gw() ran, a third state "stopped" is required to correctly signal that a backbone_gw is in the state of being cleaned up.

Gravité et risque d'exploitation

CVE-2026-64095 obtient un score CVSS de 7.1/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.27 %, ce qui la place devant 17.6 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=7.0.*, <=6.12.*, 6.12.93, 0, <1f013bc94154f2e78e97d0296175664224c796e0, <461f1e3dfb888701895b766446c55db2b10db705, 6.1.176, 5.15.210, 3.5, <=5.10.*, <=6.6.*, <5328b95960774f2e189f22485616bc7b8eb2f7e3, 6.18.34, <3.5, 7.1, <=6.18.*, 7.0.11, <a9393751ecf7e9096f93cb6eed02db4f79125765, <=*, <65497ad155a3246df177b5ef662cd6e5a32cb470, <=5.15.*, 6.6.143, 23721387c409087fd3b97e274f34d3ddc0970b74, <45384612f29692fbf0c770200361a7acff90125c, <83ab69bd12b80f6ea169c8bea6977701b53a043d, <8ff9c59d1b7b48c2596878341a5310f32895d52b, 5.10.259) 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

Rechercher une autre CVE