CVE-2025-39746: wifi: ath10k: shutdown driver when hardware is unreliable

Published Sep 11, 2025
·
Updated

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:

ath10kpci 0000:01:00.0: wmi command 20486 timeout, restarting hardware ath10kpci 0000:01:00.0: already restarting ath10kpci 0000:01:00.0: failed to stop WMI vdev 0: -11 ath10kpci 0000:01:00.0: failed to stop vdev 0: -11 ieee80211 phy0: PM: DPM device timeout Call Trace: panic+0x125/0x315 dpmwatchdogset+0x54/0x54 dpmwatchdoghandler+0x57/0x57 calltimerfn+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.

failcontcount and pendingrecovery 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

Affected Software

10 affected components
Linux Kernel
Microsoft azl3 kernel 6.6.96.2-2
Microsoft azl3 kernel 6.6.104.2-4
Linux Linux kernel>=3.11<6.12.43
Linux Linux kernel>=6.13<6.15.11
Linux Linux kernel>=6.16<6.16.2
Microsoft azl3 kernel 6.6.112.1-2
Microsoft cbl2 kernel 5.15.186.1-1
Microsoft azl3 kernel 6.6.117.1-1
Microsoft azl3 kernel 6.6.119.3-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Compensating control

    Shut down the ath10k driver when the hardware is deemed unreliable after the threshold for consecutive restart failures is exceeded.

Event History

Sep 11, 2025
CVE Published
via MITRE·04:52 PM
Data Sourced
via MITRE·04:52 PM
Description
Data Sourced
via NVD·05:15 PM
RemedyDescriptionSeverityAffected Software
Sep 13, 2025
Data Sourced
via Microsoft·01:02 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·01:02 AM
Affected Software
Updated
via Microsoft·01:02 AM
SeverityAffected Software
Updated
via Microsoft·08:02 AM
DescriptionSeverity

Frequently Asked Questions

1

What is the severity of CVE-2025-39746?

CVE-2025-39746 is classified as a high severity vulnerability due to potential system crashes and loss of connectivity.

2

How do I fix CVE-2025-39746?

To fix CVE-2025-39746, you should upgrade to the latest stable version of the Linux kernel that includes the patch addressing this vulnerability.

3

What is the impact of CVE-2025-39746 on system stability?

The impact of CVE-2025-39746 on system stability can lead to crashes during system resume when the ath10k driver encounters issues with the PCIe bus.

4

Which systems are affected by CVE-2025-39746?

CVE-2025-39746 affects systems running the Linux kernel with the ath10k wireless driver.

5

Is there a workaround for CVE-2025-39746?

A temporary workaround for CVE-2025-39746 may involve disabling the ath10k driver to prevent system crashes until a patch is applied.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203