CVE-2026-74407

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

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

wifi: ath11k: cancel SSR work items during PCI shutdown

A reboot can crash the kernel if it overlaps with WLAN firmware crash recovery (SSR). The crash is a NULL pointer dereference in the MHI teardown path while freeing DMA-backed MHI contexts.

Simplified trace: dma_free_attrs mhi_deinit_dev_ctxt [mhi] ath11k_pci_power_down [ath11k_pci] ath11k_pci_shutdown [ath11k_pci] device_shutdown kernel_restart

On the host side, SSR is driven by the MHI RDDM callback, which queues reset_work to perform device recovery. reset_work power-cycles the device by calling ath11k_hif_power_down() followed by ath11k_hif_power_up(). The power-down phase deinitializes MHI and frees DMA resources.

Shutdown/reboot runs fully asynchronously with this RDDM-driven SSR recovery flow. As a result, the shutdown path (ath11k_pci_shutdown() -> ath11k_pci_power_down()) can race with the SSR recovery sequence.

Fix this by canceling SSR-related work items during PCI shutdown, marking the device as unregistering, and serializing the RDDM callback path that checks and queues reset_work. This ensures that no new SSR recovery work can be queued once teardown has started, and that any in-flight recovery work is fully synchronized before device power-down, preventing MHI teardown and DMA resource freeing from running more than once.

Note: This issue only affects PCI/MHI-based devices. AHB-based ath11k devices do not queue reset_work in normal SSR flows.

Tested-on: WCN6855 hw2.1 PCI WLAN.HSP.1.1-04866.5-QCAHSPSWPL_V1_V2_SILICONZ_IOE-1

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
44
EG Risk 44/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
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
29th
KEV
Not listed

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

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

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

August 15, 2026

Last Modified

September 21, 2026

Advisory Details (2)

Auto-updated Aug 17, 2026
Patch available.
generic

wifi: ath11k: cancel SSR work items during PCI shutdown - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8c79aac429b583301f387374ff37c59be671df87
generic

wifi: ath11k: cancel SSR work items during PCI shutdown - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/53dd29e8aeb2a1b5f079178551836b85fc6b53df

Vendor Advisories for CVE-2026-74407(1)

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

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-azure-lts-26.04 (7.0.0-1017.17) @ resolute2026-10-06ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1015.15) @ resolute2026-10-06ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-38.38) @ resolute2026-10-06ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1035.38) @ noble2026-10-06ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (358 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (181 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (160 versions)
  • every version up to 7.1.5-1: fixed in 7.1.5-1
—

All Vendor Advisories

(4)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 34× in last 7d / 138× 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.

Showing the most recent 100 of 235 total refreshes for this CVE.

  1. 2026-10-06 22:22 UTCEG score recompute
  2. 2026-10-06 22:22 UTCVendor advisory
  3. 2026-10-06 22:22 UTCGHSA enrichment
  4. 2026-10-06 15:18 UTCEPSS rescore
  5. 2026-10-06 09:10 UTCEG score recompute
  6. 2026-10-06 09:10 UTCVendor advisory
  7. 2026-10-06 09:10 UTCGHSA enrichment
  8. 2026-10-05 17:43 UTCEPSS rescore
  9. 2026-10-05 09:41 UTCEG score recompute
  10. 2026-10-05 09:41 UTCVendor advisory
  11. 2026-10-05 09:41 UTCGHSA enrichment
  12. 2026-10-04 23:22 UTCEPSS rescore
  13. 2026-10-04 21:57 UTCVendor advisory
  14. 2026-10-04 21:57 UTCGHSA enrichment
  15. 2026-10-04 06:53 UTCVendor advisory
  16. 2026-10-04 06:53 UTCGHSA enrichment
  17. 2026-10-03 19:31 UTCEG score recompute
  18. 2026-10-03 19:31 UTCVendor advisory
  19. 2026-10-03 19:31 UTCGHSA enrichment
  20. 2026-10-03 14:26 UTCEPSS rescore
  21. 2026-10-03 03:15 UTCEG score recompute
  22. 2026-10-03 03:15 UTCVendor advisory
  23. 2026-10-03 03:15 UTCGHSA enrichment
  24. 2026-10-02 15:51 UTCVendor advisory
  25. 2026-10-02 15:51 UTCGHSA enrichment
Show 75 more
  1. 2026-10-02 02:01 UTCEG score recompute
  2. 2026-10-02 02:01 UTCVendor advisory
  3. 2026-10-02 02:01 UTCGHSA enrichment
  4. 2026-10-01 19:50 UTCEPSS rescore
  5. 2026-10-01 08:28 UTCVendor advisory
  6. 2026-10-01 08:28 UTCGHSA enrichment
  7. 2026-09-30 20:58 UTCEG score recompute
  8. 2026-09-30 20:58 UTCVendor advisory
  9. 2026-09-30 20:58 UTCGHSA enrichment
  10. 2026-09-29 15:24 UTCEPSS rescore
  11. 2026-09-28 23:45 UTCEG score recompute
  12. 2026-09-28 23:45 UTCVendor advisory
  13. 2026-09-28 23:44 UTCGHSA enrichment
  14. 2026-09-28 13:52 UTCEPSS rescore
  15. 2026-09-28 10:15 UTCVendor advisory
  16. 2026-09-28 10:15 UTCGHSA enrichment
  17. 2026-09-27 22:44 UTCEG score recompute
  18. 2026-09-27 22:44 UTCVendor advisory
  19. 2026-09-27 22:44 UTCGHSA enrichment
  20. 2026-09-27 13:48 UTCEPSS rescore
  21. 2026-09-27 08:26 UTCEG score recompute
  22. 2026-09-27 08:26 UTCVendor advisory
  23. 2026-09-27 08:26 UTCGHSA enrichment
  24. 2026-09-26 15:59 UTCEPSS rescore
  25. 2026-09-26 00:28 UTCEPSS rescore
  26. 2026-09-25 02:31 UTCEG score recompute
  27. 2026-09-25 02:31 UTCVendor advisory
  28. 2026-09-25 02:31 UTCGHSA enrichment
  29. 2026-09-24 14:04 UTCEPSS rescore
  30. 2026-09-24 10:55 UTCVendor advisory
  31. 2026-09-24 10:55 UTCGHSA enrichment
  32. 2026-09-23 23:31 UTCEG score recompute
  33. 2026-09-23 23:31 UTCVendor advisory
  34. 2026-09-23 23:31 UTCGHSA enrichment
  35. 2026-09-23 17:54 UTCEPSS rescore
  36. 2026-09-23 11:58 UTCVendor advisory
  37. 2026-09-23 11:58 UTCGHSA enrichment
  38. 2026-09-23 00:35 UTCEG score recompute
  39. 2026-09-23 00:35 UTCVendor advisory
  40. 2026-09-23 00:35 UTCGHSA enrichment
  41. 2026-09-22 16:01 UTCEPSS rescore
  42. 2026-09-22 13:12 UTCVendor advisory
  43. 2026-09-22 13:12 UTCGHSA enrichment
  44. 2026-09-22 01:48 UTCEG score recompute
  45. 2026-09-22 01:48 UTCVendor advisory
  46. 2026-09-22 01:48 UTCGHSA enrichment
  47. 2026-09-21 21:09 UTCEPSS rescore
  48. 2026-09-21 14:22 UTCEG score recompute
  49. 2026-09-21 14:22 UTCVendor advisory
  50. 2026-09-21 14:22 UTCGHSA enrichment
  51. 2026-09-21 13:21 UTCEG score recompute
  52. 2026-09-21 13:21 UTCVendor advisory
  53. 2026-09-21 13:21 UTCGHSA enrichment
  54. 2026-09-21 09:10 UTCVendor advisory
  55. 2026-09-21 09:10 UTCGHSA enrichment
  56. 2026-09-20 21:47 UTCEG score recompute
  57. 2026-09-20 21:47 UTCVendor advisory
  58. 2026-09-20 21:47 UTCGHSA enrichment
  59. 2026-09-20 20:16 UTCEPSS rescore
  60. 2026-09-20 10:23 UTCVendor advisory
  61. 2026-09-20 10:23 UTCGHSA enrichment
  62. 2026-09-19 23:00 UTCEG score recompute
  63. 2026-09-19 23:00 UTCVendor advisory
  64. 2026-09-19 23:00 UTCGHSA enrichment
  65. 2026-09-19 11:02 UTCVendor advisory
  66. 2026-09-19 11:02 UTCGHSA enrichment
  67. 2026-09-18 23:06 UTCEG score recompute
  68. 2026-09-18 23:06 UTCVendor advisory
  69. 2026-09-18 23:06 UTCGHSA enrichment
  70. 2026-09-18 19:28 UTCEPSS rescore
  71. 2026-09-18 11:43 UTCVendor advisory
  72. 2026-09-18 11:43 UTCGHSA enrichment
  73. 2026-09-18 00:20 UTCEG score recompute
  74. 2026-09-18 00:20 UTCGHSA enrichment
  75. 2026-09-17 11:12 UTCGHSA enrichment

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-74407?
CVE-2026-74407 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: cancel SSR work items during PCI shutdown A reboot can crash the kernel if it overlaps with WLAN firmware crash recovery (SSR). The crash is a NULL pointer dereference in the MHI teardown path while freeing DMA-backed…
When was CVE-2026-74407 disclosed?
CVE-2026-74407 was first published on August 15, 2026, with the most recent update on September 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74407 actively exploited?
CVE-2026-74407 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (29th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-74407?
CVE-2026-74407 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-74407?
A fix for CVE-2026-74407 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-74407 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-74407

Explore →

Is Your Infrastructure Affected by CVE-2026-74407?

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

Book a Demo →Browse All CVEs