Heimdall Security Logo

CVE-2026-97922

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, 7.2.7, bf470f051556b610265ea02ad2102de75e8e619c, 6.18.53, 0, <a1f1d64a0a9791c842c4646253daf6ac0313eac7, <b513a4c60a7aa1f4b4c2a48544ab003cb36f1e94, <4bddcb346a6cf4615ca77f69a589623b877ca267, 8bcebc77e85f3d7536f96845a0fe94b1dddb6af0, <4.20, 6.6.158, <=6.6.*, 6.1.189, <94bbd65da4ae26592fa1977a74ee94218ab02a26, ce28d664054df01997baace61d1defca77689798, <5.5, <=6.18.*, 5.5, 5.4.16, 4.19.100, <=7.2.*, <=*, <e7b6d67b43caee9183a4374d23641578ea556e6c, <4cff53bb19412c6f2d90b50678de5c3903f7f96a, 6.12.111, 7.3

Description

In the Linux kernel, the following vulnerability has been resolved: tracing: Free histogram var refs regardless of how often they are referenced Using the same variable three or more times in one hist trigger leaks the variable reference and its strings when the trigger is removed. commit 656fe2ba85e8 ("tracing: Use hist trigger's var_ref array to destroy var_refs") made a trigger's var_refs[] array the only owner of a var ref: destroy_hist_field() returns early for HIST_FIELD_FL_VAR_REF, so the field expressions never destroy one. One entry, freed once, no count needed. commit 8bcebc77e85f ("tracing: Fix histogram code when expression has same var as value") then made repeated references share one object and added a count of them. Only the increment side exists, since those expressions still return early and never drop a reference, so __destroy_hist_field() sees how many references were created rather than how many are left. It frees when the decremented count is 0 or 1, so two references work and three or more leak. Sharing kept one array entry per object, and create_var_ref() searches and appends within a single trigger, so nothing outside it holds the object. Removing a trigger whose variables are still referenced is already refused by check_var_refs() with -EBUSY. Drop the count and free unconditionally.

Gravité et risque d'exploitation

CVE-2026-97922 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.21 %, ce qui la place devant 9.9 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, 7.2.7, bf470f051556b610265ea02ad2102de75e8e619c, 6.18.53, 0, <a1f1d64a0a9791c842c4646253daf6ac0313eac7, <b513a4c60a7aa1f4b4c2a48544ab003cb36f1e94, <4bddcb346a6cf4615ca77f69a589623b877ca267, 8bcebc77e85f3d7536f96845a0fe94b1dddb6af0, <4.20, 6.6.158, <=6.6.*, 6.1.189, <94bbd65da4ae26592fa1977a74ee94218ab02a26, ce28d664054df01997baace61d1defca77689798, <5.5, <=6.18.*, 5.5, 5.4.16, 4.19.100, <=7.2.*, <=*, <e7b6d67b43caee9183a4374d23641578ea556e6c, <4cff53bb19412c6f2d90b50678de5c3903f7f96a, 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

Rechercher une autre CVE