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.
Published: 2026-09-24
Score: 5.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Denial of Service
Action: Immediate Patch
AI Analysis

Impact

The iwlwifi driver in the Linux kernel contains a flaw where a P2P‑Device can be removed from its binding after a remain‑on‑channel operation while its PHY context is retained as a cache. If a subsequent binding update re‑adds the same P2P‑Device, the driver attempts to use the stale context, causing a firmware crash. This results in a loss of Wi‑Fi functionality; no code execution is achieved, but the crash constitutes a denial‑of‑service fault in the network subsystem. The weakness is a use‑after‑free scenario identified as CWE‑825.

Affected Systems

Linux kernel installations that include the iwlwifi driver and have not yet applied the commit that introduces a boolean guard for P2P‑Device binding restoration. All distributions shipping kernels pre‑commit 7be2fc679c8f657868988e41c0bb15bf5a454620 are affected. The problem is limited to hardware that uses the iwlwifi driver for Intel wireless chips.

Risk and Exploitability

The vulnerability is a local denial‑of‑service condition; the likely attack vector requires interaction with the Wi‑Fi stack and can be triggered through a specific sequence of channel operations. EPSS is < 1%, and the vulnerability is not listed in CISA's KEV catalog, indicating no evidence of widespread exploitation. The CVSS score of 5.5 reflects moderate impact on availability. While the description itself implies a local exploitation scenario, the exact external reach of the flaw is inferred based on the need to manipulate Wi‑Fi channel operations from the device side.

Generated by OpenCVE AI on October 1, 2026 at 16:13 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest kernel update that incorporates the iwlwifi binding fix.
  • If a kernel upgrade cannot be performed immediately, disable P2P or remain‑on‑channel functionality in the Wi‑Fi driver configuration to prevent the problematic binding scenario.
  • Monitor system logs for firmware crashes and confirm that the driver no longer re‑adds removed P2P‑Devices.

Generated by OpenCVE AI on October 1, 2026 at 16:13 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 30 Sep 2026 00:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-825
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate


Thu, 24 Sep 2026 16:30:00 +0000

Type Values Removed Values Added
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.
Title wifi: iwlwifi: mvm: fix P2P-Device binding handling
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-09-25T12:44:08.867Z

Reserved: 2026-09-24T14:53:16.869Z

Link: CVE-2026-97432

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-24T17:17:21.237

Modified: 2026-09-25T13:17:26.827

Link: CVE-2026-97432

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-09-24T00:00:00Z

Links: CVE-2026-97432 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-10-01T16:15:10Z

Weaknesses
  • CWE-825

    Expired Pointer Dereference