CVE-2026-97432

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