Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-97474 high CVSS 7.4

Vulnerability in Linux kernel (CVE-2026-97474)

Summary

Vulnerability in Linux kernel (CVE-2026-97474). Successful exploitation can lead to full system takeover.

Original description

The description as published by the source.

In the Linux kernel, the following vulnerability has been resolved:

wifi: iwlwifi: mld: purge async notifications upon nic error

This fixes a kernel panic in reconfig failure:

  1. we have a BSS connection
  2. we have a NAN connection
  3. FW error occurs
  4. reconfig restores the BSS connection
  5. however, restoring the NAN connection fails due to a FW error.
  6. erroneously, ieee80211_handle_reconfig_failure is called and marks all
    interfaces as not-in-driver (will be fixed in a different patch).
  7. mac80211 frees the links of the BSS connection but doesn't tell the
    driver about that, as it thinks that this vif is not in the driver.
  8. in ieee80211_stop_device, ALL wiphy works are getting flushed
    (erroneously?)
  9. Therefore, async_handlers_wk is being executed, processing the
    statistics notification that was received after we restored the BSS
    connection.
  10. the notification handler dereferences fw_id_to_bss_conf[id], which is
    now a dangling pointer, as mac80211 already freed this link in (7).
  11. On the first access to one of the links fields, we panic.

While this can and should be fixed by removing the call to
ieee80211_handle_reconfig_failure in (6), it is also not a good idea to
carry and maybe handle notifications from a dead FW.

We do purge the notifications when we stop the FW, but in reconfig
failure we stop the FW too late, after the notifications are processed.
In addition, async_handlers_wk can always be scheduled before the
reconfig work.

Pur…

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-97474 has been found in Linux kernel.
Successful exploitation can lead to full system takeover. CVSS score: 7.4/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Linux kernel CVE-2026-97474" on the vendor's site.

CVE-2026-97474 (Linux kernel) — CVSS v3 7.4
Attack vector: local / unauthenticated / no user interaction
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: High (CVSS 7.4/10). Successful exploitation can lead to full system takeover.

🔧 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 でアラート再発が無いか継続監視。

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