Answer in brief
CVE-2022-49519 records a High severity (CVSS 8.8) vulnerability in ath10k: skip ath10k_halt during suspend for driver state RESTARTING. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), 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 8.8. 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), 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 <8aa3750986ffcf73e0692db3b40dd3a8e8c0c575 || >=5e3dd157d7e70f0e3cea3f2573ed69fb156a19d5 <c2272428090d0d215a3f017cbbbad731c07eee53 || >=5e3dd157d7e70f0e3cea3f2573ed69fb156a19d5 <7eb14cb604f49e58b7cf6faa87961a865a3c8649 || >=5e3dd157d7e70f0e3cea3f2573ed69fb156a19d5 <5321e5211b5dc873e2e3d0deb749e69ecf4dbfe5 || >=5e3dd157d7e70f0e3cea3f2573ed69fb156a19d5 <b72a4aff947ba807177bdabb43debaf2c66bee05 | 8aa3750986ffcf73e0692db3b40dd3a8e8c0c575, c2272428090d0d215a3f017cbbbad731c07eee53, 7eb14cb604f49e58b7cf6faa87961a865a3c8649, 5321e5211b5dc873e2e3d0deb749e69ecf4dbfe5, b72a4aff947ba807177bdabb43debaf2c66bee05 |
| Linux/Linuxgeneric | 3.11 | Not reported |
| Linux/Linuxgeneric | >=c2cac2f74ab4bcf0db0dcf3a612f1e5b52d145c8 <8aa3750986ffcf73e0692db3b40dd3a8e8c0c575 || >=c2cac2f74ab4bcf0db0dcf3a612f1e5b52d145c8 <c2272428090d0d215a3f017cbbbad731c07eee53 || >=c2cac2f74ab4bcf0db0dcf3a612f1e5b52d145c8 <7eb14cb604f49e58b7cf6faa87961a865a3c8649 || >=c2cac2f74ab4bcf0db0dcf3a612f1e5b52d145c8 <5321e5211b5dc873e2e3d0deb749e69ecf4dbfe5 || >=c2cac2f74ab4bcf0db0dcf3a612f1e5b52d145c8 <b72a4aff947ba807177bdabb43debaf2c66bee05 || ea23fca0c60045afbbeceef1926893d905eb1b36 || >=4.9.2 <4.10 | 8aa3750986ffcf73e0692db3b40dd3a8e8c0c575, c2272428090d0d215a3f017cbbbad731c07eee53, 7eb14cb604f49e58b7cf6faa87961a865a3c8649, 5321e5211b5dc873e2e3d0deb749e69ecf4dbfe5, b72a4aff947ba807177bdabb43debaf2c66bee05, 4.10 |
| Linux/Linuxgeneric | 4.10 | Not reported |
Published upstream
Feb 26, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: ath10k: skip ath10k_halt during suspend for driver state RESTARTING Double free crash is observed when FW recovery(caused by wmi timeout/crash) is followed by immediate suspend event. The FW recovery is triggered by ath10k_core_restart() which calls driver clean up via ath10k_halt(). When the suspend event occurs between the FW recovery, the restart worker thread is put into frozen state until suspend completes. The suspend event triggers ath10k_stop() which again triggers ath10k_halt() The double invocation of ath10k_halt() causes ath10k_htt_rx_free() to be called twice(Note: ath10k_htt_rx_alloc was not called by restart worker thread because of its frozen state), causing the crash. To fix this, during the suspend flow, skip call to ath10k_halt() in ath10k_stop() when the current driver state is ATH10K_STATE_RESTARTING. Also, for driver state ATH10K_STATE_RESTARTING, call ath10k_wait_for_suspend() in ath10k_stop(). This is because call to ath10k_wait_for_suspend() is skipped later in [ath10k_halt() > ath10k_core_stop()] for the driver state ATH10K_STATE_RESTARTING. The frozen restart worker thread will be cancelled during resume when the device comes out of suspend. Below is the crash stack for reference: [ 428.469167] ------------[ cut here ]------------ [ 428.469180] kernel BUG at mm/slub.c:4150! [ 428.469193] invalid opcode: 0000 [#1] PREEMPT SMP NOPTI [ 428.469219] Workqueue: events_unbound async_run_entry_fn [ 428.469230] RIP: 0010:kfree+0x319/0x31b [ 428.469241] RSP: 0018:ffffa1fac015fc30 EFLAGS: 00010246 [ 428.469247] RAX: ffffedb10419d108 RBX: ffff8c05262b0000 [ 428.469252] RDX: ffff8c04a8c07000 RSI: 0000000000000000 [ 428.469256] RBP: ffffa1fac015fc78 R08: 0000000000000000 [ 428.469276] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 428.469285] Call Trace: [ 428.469295] ? dma_free_attrs+0x5f/0x7d [ 428.469320] ath10k_core_stop+0x5b/0x6f [ 428.469336] ath10k_halt+0x126/0x177 [ 428.469352] ath10k_stop+0x41/0x7e [ 428.469387] drv_stop+0x88/0x10e [ 428.469410] __ieee80211_suspend+0x297/0x411 [ 428.469441] rdev_suspend+0x6e/0xd0 [ 428.469462] wiphy_suspend+0xb1/0x105 [ 428.469483] ? name_show+0x2d/0x2d [ 428.469490] dpm_run_callback+0x8c/0x126 [ 428.469511] ? name_show+0x2d/0x2d [ 428.469517] __device_suspend+0x2e7/0x41b [ 428.469523] async_suspend+0x1f/0x93 [ 428.469529] async_run_entry_fn+0x3d/0xd1 [ 428.469535] process_one_work+0x1b1/0x329 [ 428.469541] worker_thread+0x213/0x372 [ 428.469547] kthread+0x150/0x15f [ 428.469552] ? pr_cont_work+0x58/0x58 [ 428.469558] ? kthread_blkcg+0x31/0x31 Tested-on: QCA6174 hw3.2 PCI WLAN.RM.4.4.1-00288-QCARMSWPZ-1
Quoted source text, attributed separately from HOL analysis.