CVE-2026-63834

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <1111a3381bca2d1f084a07686bc783af5ab23df7, <=6.1.*, <=6.12.*, 6.6.144, <e7c775110e1858e5a7471a23a9c9658c0af9df89, 5.15.211, 0, <=7.1.*, 5.10.260, <f8c499fd275e59203b77fca76ae6ef2d096c2133, <2233787658db859f0a9b83cb397cf783bb8be865, <=5.10.*, <=6.6.*, 6.12.95, <1c616b0be4bd8399d485e25e91859373b95d6013, <c6231d628d06d841bc1617b2f7034f5f39876b16, <=6.18.*, 6.1.177, 6.18.38, 33a3bb4a3345bb511f9c69c913da95d4693e2a4e, 4.8, <=*, <=5.15.*, 7.1.3, <1fb8762600a393d1caccd63be5d07e1756982d68, <4.8, 7.2, <31a88792bfba142be3c9521538c1db805677381f

Description

In the Linux kernel, the following vulnerability has been resolved: batman-adv: tp_meter: restrict number of unacked list entries When the unacked_list is unbound, an attacker could send messages with small lengths and appropriated seqno + gaps to force the receiver to allocate more and more unacked_list entries. And the end either causing an out-of-memory situation or increase the management overhead for the (large) list that significant portions of CPU cycles are wasted in searching through the list. When limiting the list to a specific number, it is important to still correctly add a new entry to the list. But if the list became larger than the limit, the last entry of the list (with the highest seqno) must be dropped to still allow the earlier seqnos to finish and therefore to continue the process. Otherwise, the process might get stuck with too high seqnos which are not handled by batadv_tp_ack_unordered().

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <1111a3381bca2d1f084a07686bc783af5ab23df7, <=6.1.*, <=6.12.*, 6.6.144, <e7c775110e1858e5a7471a23a9c9658c0af9df89, 5.15.211, 0, <=7.1.*, 5.10.260, <f8c499fd275e59203b77fca76ae6ef2d096c2133, <2233787658db859f0a9b83cb397cf783bb8be865, <=5.10.*, <=6.6.*, 6.12.95, <1c616b0be4bd8399d485e25e91859373b95d6013, <c6231d628d06d841bc1617b2f7034f5f39876b16, <=6.18.*, 6.1.177, 6.18.38, 33a3bb4a3345bb511f9c69c913da95d4693e2a4e, 4.8, <=*, <=5.15.*, 7.1.3, <1fb8762600a393d1caccd63be5d07e1756982d68, <4.8, 7.2, <31a88792bfba142be3c9521538c1db805677381f) 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