CVE-2026-97474

HIGHPre-NVD 7.47.4—
EchelonGraph scoreHIGH confidence

Score 7.4 from GitHub Security Advisory (severity: HIGH) published 2026-09-24. A secondary CVSS source baseline 7.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.4EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.4Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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:

  • we have a BSS connection
  • we have a NAN connection
  • FW error occurs
  • reconfig restores the BSS connection
  • however, restoring the NAN connection fails due to a FW error.
  • erroneously, ieee80211_handle_reconfig_failure is called and marks all
interfaces as not-in-driver (will be fixed in a different patch).
  • 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.
  • in ieee80211_stop_device, *ALL* wiphy works are getting flushed
(erroneously?)
  • Therefore, async_handlers_wk is being executed, processing the
statistics notification that was received after we restored the BSS connection.
  • the notification handler dereferences fw_id_to_bss_conf[id], which is
now a dangling pointer, as mac80211 already freed this link in (7).
  • 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.

Purge the notifications immediately when transport notifies about a nic error.

CVSS v3
7.4
EG Score
7.4HIGHhigh confidence
EG Risk
38
EG Risk 38/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity74% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.1%
EPSS %ILE
1st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 24, 2026

Last Modified

September 28, 2026

Advisory Details (2)

Auto-updated Sep 25, 2026
No patch confirmed yet.
generic

wifi: iwlwifi: mld: purge async notifications upon nic error - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a40ad60a47f7c904b75a9ff83b39edebf3961c85
generic

wifi: iwlwifi: mld: purge async notifications upon nic error - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1b3b7b521041d55459f8457db8921e9778482063

Vendor Advisories for CVE-2026-97474(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (177 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 38× in last 7d / 59× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-04 23:23 UTCEPSS rescore
  2. 2026-10-04 20:53 UTCVendor advisory
  3. 2026-10-04 20:53 UTCGHSA enrichment
  4. 2026-10-04 07:55 UTCVendor advisory
  5. 2026-10-04 07:55 UTCGHSA enrichment
  6. 2026-10-03 18:56 UTCEG score recompute
  7. 2026-10-03 18:56 UTCVendor advisory
  8. 2026-10-03 18:56 UTCGHSA enrichment
  9. 2026-10-03 14:26 UTCEPSS rescore
  10. 2026-10-03 05:58 UTCEG score recompute
  11. 2026-10-03 05:58 UTCVendor advisory
  12. 2026-10-03 05:58 UTCGHSA enrichment
  13. 2026-10-02 17:57 UTCEPSS rescore
  14. 2026-10-02 16:59 UTCVendor advisory
  15. 2026-10-02 16:59 UTCGHSA enrichment
  16. 2026-10-02 04:02 UTCEG score recompute
  17. 2026-10-02 04:02 UTCVendor advisory
  18. 2026-10-02 04:01 UTCGHSA enrichment
  19. 2026-10-01 19:51 UTCEPSS rescore
  20. 2026-10-01 15:01 UTCVendor advisory
  21. 2026-10-01 15:01 UTCGHSA enrichment
  22. 2026-10-01 02:04 UTCEG score recompute
  23. 2026-10-01 02:04 UTCVendor advisory
  24. 2026-10-01 02:03 UTCGHSA enrichment
  25. 2026-09-30 15:04 UTCEPSS rescore
Show 34 more
  1. 2026-09-30 13:04 UTCVendor advisory
  2. 2026-09-30 13:04 UTCGHSA enrichment
  3. 2026-09-29 23:54 UTCEG score recompute
  4. 2026-09-29 23:54 UTCVendor advisory
  5. 2026-09-29 23:54 UTCGHSA enrichment
  6. 2026-09-29 08:32 UTCEG score recompute
  7. 2026-09-29 08:32 UTCVendor advisory
  8. 2026-09-29 08:32 UTCGHSA enrichment
  9. 2026-09-28 19:33 UTCEG score recompute
  10. 2026-09-28 19:33 UTCVendor advisory
  11. 2026-09-28 19:32 UTCGHSA enrichment
  12. 2026-09-28 13:52 UTCEPSS rescore
  13. 2026-09-28 13:52 UTCEPSS rescore
  14. 2026-09-28 06:24 UTCEG score recompute
  15. 2026-09-28 06:24 UTCGHSA enrichment
  16. 2026-09-28 05:48 UTCEG score recompute
  17. 2026-09-28 05:48 UTCGHSA enrichment
  18. 2026-09-27 22:12 UTCEG score recompute
  19. 2026-09-27 22:11 UTCGHSA enrichment
  20. 2026-09-27 13:49 UTCEPSS rescore
  21. 2026-09-27 09:11 UTCGHSA enrichment
  22. 2026-09-26 20:13 UTCEG score recompute
  23. 2026-09-26 20:13 UTCGHSA enrichment
  24. 2026-09-26 15:59 UTCEPSS rescore
  25. 2026-09-26 07:14 UTCEG score recompute
  26. 2026-09-26 07:14 UTCGHSA enrichment
  27. 2026-09-25 18:16 UTCEG score recompute
  28. 2026-09-25 18:16 UTCGHSA enrichment
  29. 2026-09-25 05:17 UTCEG score recompute▲ 7.40
  30. 2026-09-25 05:17 UTCGHSA enrichment
  31. 2026-09-25 05:16 UTCMITRE cvelistV5CVSS v3 → 7.4 · severity → HIGH
  32. 2026-09-24 17:33 UTCNVD update
  33. 2026-09-24 16:28 UTCEG score recompute
  34. 2026-09-24 16:26 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-97474?
CVE-2026-97474 is a high vulnerability published on September 24, 2026. 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.…
When was CVE-2026-97474 disclosed?
CVE-2026-97474 was first published on September 24, 2026, with the most recent update on September 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-97474 actively exploited?
CVE-2026-97474 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-97474?
CVE-2026-97474 has a CVSS base score of 7.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-97474?
No fix for CVE-2026-97474 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-97474 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-97474

Explore →

Is Your Infrastructure Affected by CVE-2026-97474?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs