CVE-2026-98130

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

CVSS 8.1 · Élevée
EPSS 0.6%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, <3d698d1e6c8bc41e3e1707777a016f1bdd07842d, 7.2.7, <09e7f9290d63178f56095d5c18fb9f9470153db5, 6.18.53, 0, <755d70ca845fd9b87c7b338ae6ae832b08cd0005, <4.20, <5.7, 5.10.271, 6.6.158, <=5.10.*, <=6.6.*, <3205a20f837f5b1f009427ac3d9f706bf8a6fbec, 6.1.189, 20a785aa52c82246055a089e55df9dac47d67da1, <cbf2df9aac4202f9fb0b361a7fe8c79b29fad92c, 9c0a4652f750afe3b4468cbcd9335b244ce2facd, <5.5, <=6.18.*, 5.15.222, 085bb270b4b1168c93afb37bbafc881207d15443, 4.19.126, <00b841bac10230c557be6b38efc48508198fe23e, <=7.2.*, 5.7, 5.4.44, <=*, <=5.15.*, <e42ba56281ca3ae2dcb3558bebee9a1c9a4831d9, <2188569e7e1b0bc3f3b557dc97ab7a02befc11c8, 5.6.16, 70989e501fbce502198d82da88358ce453575a05, 6.12.111, 7.3

Description

In the Linux kernel, the following vulnerability has been resolved: sctp: fix a TOCTOU race in SCTP_CMD_TIMER_START The SCTP_CMD_TIMER_START handler checks timer_pending() before calling timer_reduce(). The timer can expire and detach between these operations, causing timer_reduce() to rearm the timer without taking the association reference required for the newly armed timer. The timer callback later unconditionally drops its association reference, which can leave the association reference count unbalanced and result in use-after-free during association teardown. Use the return value of timer_reduce() to determine whether the timer was actually armed. Take the association reference only when timer_reduce() successfully starts a new timer, closing the race between checking the timer state and rearming it. This issue was reported by Nico Yip (@_cyeaa_) working with TrendAI Zero Day Initiative.

Gravité et risque d'exploitation

CVE-2026-98130 obtient un score CVSS de 8.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.58 %, ce qui la place devant 46.5 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, <3d698d1e6c8bc41e3e1707777a016f1bdd07842d, 7.2.7, <09e7f9290d63178f56095d5c18fb9f9470153db5, 6.18.53, 0, <755d70ca845fd9b87c7b338ae6ae832b08cd0005, <4.20, <5.7, 5.10.271, 6.6.158, <=5.10.*, <=6.6.*, <3205a20f837f5b1f009427ac3d9f706bf8a6fbec, 6.1.189, 20a785aa52c82246055a089e55df9dac47d67da1, <cbf2df9aac4202f9fb0b361a7fe8c79b29fad92c, 9c0a4652f750afe3b4468cbcd9335b244ce2facd, <5.5, <=6.18.*, 5.15.222, 085bb270b4b1168c93afb37bbafc881207d15443, 4.19.126, <00b841bac10230c557be6b38efc48508198fe23e, <=7.2.*, 5.7, 5.4.44, <=*, <=5.15.*, <e42ba56281ca3ae2dcb3558bebee9a1c9a4831d9, <2188569e7e1b0bc3f3b557dc97ab7a02befc11c8, 5.6.16, 70989e501fbce502198d82da88358ce453575a05, 6.12.111, 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