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.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
64c277f6329818db3124c9759cb9acf0f6070a54 to < 50bf37362362c8f03ab1aeab866b7fb08b262204affected84ef7cbe90e9e54c71c1da4e645ba34e1b33da77 to < 8575514a979490c9d4517fcf19b4e19119c27702affected84ef7cbe90e9e54c71c1da4e645ba34e1b33da77 to < 7be2fc679c8f657868988e41c0bb15bf5a454620affected84ef7cbe90e9e54c71c1da4e645ba34e1b33da77 to < b74e377cad9271950c57472867c469e4b5b2ff0caffected8ddf2212cfa5d9ef4fd289ce0d9dda728f2160b8affected6.6.2 to < 6.6.160affected6.5.12 to < 6.6affected
Linux Linux
Default version status: affected
6.7affected0 to < 6.7unaffected6.6.160 to ≤ 6.6.*unaffected6.12.114 to ≤ 6.12.*unaffected6.18.53 to ≤ 6.18.*unaffected7.2 to ≤ *unaffected