CVE-2026-97432

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : 64c277f6329818db3124c9759cb9acf0f6070a54, 7.2, <=*, <6.6, <7be2fc679c8f657868988e41c0bb15bf5a454620, 8ddf2212cfa5d9ef4fd289ce0d9dda728f2160b8, <b74e377cad9271950c57472867c469e4b5b2ff0c, <=6.18.*, 6.6.2, 6.7, 0, 6.18.53, 84ef7cbe90e9e54c71c1da4e645ba34e1b33da77, 6.5.12, <6.7

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: mvm: fix P2P-Device binding handling Our binding handling for P2P-Device can run into the following scenario, as observed by our testing: - a station interface is connected on some channel - the P2P-Device does a remain-on-channel (ROC) on that channel - the ROC ends, and the P2P-Device is removed from the binding, but the phy_ctxt pointer is left around as a PHY cache so we don't need to recalibrate to the channel again and again in case it's not shared - a binding update by the station interface, even a removal, will re-add the P2P-Device to the binding - the P2P-Device is removed, which removes the PHY context, but it's still in the binding so the firmware crashes Since the P2P device is removed from the binding and only re- added by unrelated code, but we want to keep the phy_ctxt around as a cache for future ROC usage, fix it by adding a boolean that indicates whether or not the P2P-Device should be added to the binding, and handle that in the binding iterator. That way, the station interface cannot re-add the P2P-Device to the binding when that isn't active.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions 64c277f6329818db3124c9759cb9acf0f6070a54, 7.2, <=*, <6.6, <7be2fc679c8f657868988e41c0bb15bf5a454620, 8ddf2212cfa5d9ef4fd289ce0d9dda728f2160b8, <b74e377cad9271950c57472867c469e4b5b2ff0c, <=6.18.*, 6.6.2, 6.7, 0, 6.18.53, 84ef7cbe90e9e54c71c1da4e645ba34e1b33da77, 6.5.12, <6.7) 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