Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-97432

Vulnerability in Linux kernel (CVE-2026-97432)

Summary

Vulnerability in Linux kernel (CVE-2026-97432). Risk of unauthorized operations or information disclosure.

Original description

The description as published by the source.

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: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-97432 has been found in Linux kernel.
Risk of unauthorized operations or information disclosure.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Linux kernel CVE-2026-97432" on the vendor's site.

CVE-2026-97432 (Linux kernel)
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in Linux kernel.

📍 Affected scope

Check the vendor advisory for the affected versions of Linux kernel.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Linux kernel を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Linux Kernel
[{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.18.53"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details