Vulnerability · CVE-2025-37794
In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: Purge vif txq in ieee80211_do_stop() After ieee80211_do_stop() SKB from vif's txq could still be
Published May 1, 2025 · catalog updated May 11, 2026 · Linux Linux
Check if you run it
No confirmed exploitation is on record for CVE-2025-37794. EPSS is 0.20%. Act only if a listed version of Linux Linux is installed.
Gaps on this record
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- None0.0
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.20%
- Remediation
- Version ranges on file
- Affected products
- vendor Linux Linux ba8c3d6f16a1f9305c23ac1d2fd3992508c5ac03 <305741e7e63234cbcf9b5c4e6aeca25ba0834be8
In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: Purge vif txq in ieee80211_do_stop() After ieee80211_do_stop() SKB from vif's txq could still be processed. Indeed another concurrent vif schedule_and_wake_txq call could cause those packets to be dequeued (see ieee80211_handle_wake_tx_queue()) without checking the sdata current state. Because vif.drv_priv is now cleared in this function, this could lead to driver crash. For example in ath12k, ahvif is store in vif.drv_priv. Thus if ath12k_mac_op_tx() is called after ieee80211_do_stop(), ahvif->ah can be NULL,
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- vendor Linux Linux ba8c3d6f16a1f9305c23ac1d2fd3992508c5ac03 <305741e7e63234cbcf9b5c4e6aeca25ba0834be8ba8c3d6f16a1f9305c23ac1d2fd3992508c5ac03 <305741e7e63234cbcf9b5c4e6aeca25ba0834be8
How to fix CVE-2025-37794
Recommended remediation
Affected version ranges suggest a fixed boundary. Verify against the vendor advisory for your release.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2025-37794. EPSS is 0.20%. Act only if a listed version of Linux Linux is installed.
Which versions are affected?
Compare what you have installed with Linux Linux ba8c3d6f16a1f9305c23ac1d2fd3992508c5ac03 <305741e7e63234cbcf9b5c4e6aeca25ba0834be8 ba8c3d6f16a1f9305c23ac1d2fd3992508c5ac03 <305741e7e63234cbcf9b5c4e6aeca25ba0834be8. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 0.20%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
May 1, 2025 · EUVD
Detected
In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: Purge vif txq in ieee80211_do_stop() After ieee80211_do_stop() SKB from vif's txq could still be processed. Indeed another concurrent vif schedule_and_wake_txq call could cause those packets to be dequeued (see ieee80211_handle_wake_tx_queue()) without checking the sdata current state. Because vif.drv_priv is now c
May 11, 2026 · EUVD
Updated
In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: Purge vif txq in ieee80211_do_stop() After ieee80211_do_stop() SKB from vif's txq could still be processed. Indeed another concurrent vif schedule_and_wake_txq call could cause those packets to be dequeued (see ieee80211_handle_wake_tx_queue()) without checking the sdata current state. Because vif.drv_priv is now c
Sources
- CVE.orgVulnerability recordCVE-2025-37794
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2025-37794
30-day exploitation probability 0.2%
first.org - EUVDVulnerability recordEUVD-2025-13012
In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: Purge vif txq in ieee80211_do_stop() After ieee80211_do_stop() SKB from vif's txq could still be processed. Indeed another concurrent vif schedule_and_wake_txq call could cause those packets to be
euvd.enisa.europa.eu
References
Freshness
Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.