Answer in brief
CVE-2025-39746 records a Medium severity (CVSS 5.5) vulnerability in wifi: ath10k: shutdown driver when hardware is unreliable. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=5e3dd157d7e70f0e3cea3f2573ed69fb156a19d5 <201c9b4485edc618863a60f97a2d88bddd139467 || >=5e3dd157d7e70f0e3cea3f2573ed69fb156a19d5 <e36991bddf8be63e79659f654cdb1722db4e8132 || >=5e3dd157d7e70f0e3cea3f2573ed69fb156a19d5 <84ca5632b8d05d1c2e25604d1d63434b2fb61c85 || >=5e3dd157d7e70f0e3cea3f2573ed69fb156a19d5 <c256a94d1b1b15109740306f7f2a7c2173e12072 | 201c9b4485edc618863a60f97a2d88bddd139467, e36991bddf8be63e79659f654cdb1722db4e8132, 84ca5632b8d05d1c2e25604d1d63434b2fb61c85, c256a94d1b1b15109740306f7f2a7c2173e12072 |
| Linux/Linuxgeneric | 3.11 | Not reported |
Published upstream
Sep 11, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 28, 2026
In the Linux kernel, the following vulnerability has been resolved: wifi: ath10k: shutdown driver when hardware is unreliable In rare cases, ath10k may lose connection with the PCIe bus due to some unknown reasons, which could further lead to system crashes during resuming due to watchdog timeout: ath10k_pci 0000:01:00.0: wmi command 20486 timeout, restarting hardware ath10k_pci 0000:01:00.0: already restarting ath10k_pci 0000:01:00.0: failed to stop WMI vdev 0: -11 ath10k_pci 0000:01:00.0: failed to stop vdev 0: -11 ieee80211 phy0: PM: **** DPM device timeout **** Call Trace: panic+0x125/0x315 dpm_watchdog_set+0x54/0x54 dpm_watchdog_handler+0x57/0x57 call_timer_fn+0x31/0x13c At this point, all WMI commands will timeout and attempt to restart device. So set a threshold for consecutive restart failures. If the threshold is exceeded, consider the hardware is unreliable and all ath10k operations should be skipped to avoid system crash. fail_cont_count and pending_recovery are atomic variables, and do not involve complex conditional logic. Therefore, even if recovery check and reconfig complete are executed concurrently, the recovery mechanism will not be broken. Tested-on: QCA6174 hw3.2 PCI WLAN.RM.4.4.1-00288-QCARMSWPZ-1
Quoted source text, attributed separately from HOL analysis.