CVE-2026-97432

CVE CVE-2026-97432EUVD EUVD-2026-86045Published 2026-09-24T16:03:45.000ZLast changed 2026-09-25T12:44:08.000Z

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux 84ef7cbe90e9e54c71c1da4e645ba34e1b33da77 <b74e377cad9271950c57472867c469e4b5b2ff0c; 84ef7cbe90e9e54c71c1da4e645ba34e1b33da77 <7be2fc679c8f657868988e41c0bb15bf5a454620; 6.7; 64c277f6329818db3124c9759cb9acf0f6070a54; 6.5.12 <6.6; patch: 6.18.53; patch: 0; 8ddf2212cfa5d9ef4fd289ce0d9dda728f2160b8; 6.6.2 <6.7; patch: 7.2

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.