---
id: CVE-2026-97432
title: |-
  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 …
summary: |-
  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 …
severity: none
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <
    7be2fc679c8f657868988e41c0bb15bf5a454620
  - >-
    Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <
    b74e377cad9271950c57472867c469e4b5b2ff0c
  - Linux < 6.18.53
  - Linux (all versions)
published: '2026-09-24'
updated: '2026-09-24'
sourceUpdated: '2026-09-24T17:17:21.237'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-97432'
references:
  - url: 'https://git.kernel.org/stable/c/7be2fc679c8f657868988e41c0bb15bf5a454620'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/b74e377cad9271950c57472867c469e4b5b2ff0c'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
  - cve.org
ingestedAt: '2026-09-24T16:47:15.881Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.