CVE-2024-58096wifi: ath11k: add srng->lock for ath11k_hal_srng_* in monitor mode
- 8.8HighCVSS base score
- 0.32%Exploitation in 30 daysEPSS · top 75% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: add srng->lock for ath11k_hal_srng_* in monitor mode ath11k_hal_srng_* should be used with srng->lock to protect srng data. For ath11k_dp_rx_mon_dest_process() and ath11k_dp_full_mon_process_rx(), they use ath11k_hal_srng_* for many times but never call srng->lock. So when running (full) monitor mode, warning will occur: RIP: 0010:ath11k_hal_srng_dst_peek+0x18/0x30 [ath11k] Call Trace: ? ath11k_hal_srng_dst_peek+0x18/0x30 [ath11k] ath11k_dp_rx_process_mon_status+0xc45/0x1190 [ath11k] ? idr_alloc_u32+0x97/0xd0 ath11k_dp_rx_process_mon_rings+0x32a/0x550 [ath11k] ath11k_dp_service_srng+0x289/0x5a0 [ath11k] ath11k_pcic_ext_grp_napi_poll+0x30/0xd0 [ath11k] __napi_poll+0x30/0x1f0 net_rx_action+0x198/0x320 __do_softirq+0xdd/0x319 So add srng->lock for them to avoid such warnings. Inorder to fetch the srng->lock, should change srng's definition from 'void' to 'struct hal_srng'. And initialize them elsewhere to prevent one line of code from being too long. This is consistent with other ring process functions, such as ath11k_dp_process_rx(). Tested-on: WCN6855 hw2.0 PCI WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.30 Tested-on: QCN9074 hw1.0 PCI WLAN.HK.2.7.0.1-01744-QCAHKSWPL_SILICONZ-1
Timeline
ID reserved
By Linux
- 41 days later
· 41 days later
Published
- 19 months later
· 19 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High8.8 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.32% · top 75% of all CVEs (17 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.
Affected products
- affected d5c65159f2895379e11ca13f62feabe93278985d – < b7cc16629ae391c8ba44464ca29fcbbc1a3e1336
- affected d5c65159f2895379e11ca13f62feabe93278985d – < 27ca8004ba93a0665faa6d477eaeb551e03de6c8
- affected d5c65159f2895379e11ca13f62feabe93278985d – < 1d2178918efc928e11bed9631469ef79ff0a862a
- affected d5c65159f2895379e11ca13f62feabe93278985d – < b85758e76b6452740fc2a08ced6759af64c0d59a
- affected d5c65159f2895379e11ca13f62feabe93278985d – < 63b7af49496d0e32f7a748b6af3361ec138b1bd3
- affected 5.6
- unaffected < 5.6
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.123 – ≤ 6.6.*
- unaffected 6.12.69 – ≤ 6.12.*
- unaffected 6.14.2 – ≤ 6.14.*
- unaffected 6.15 – ≤ *
References
References5
- https://git.kernel.org/stable/c/b7cc16629ae391c8ba44464ca29fcbbc1a3e1336 (opens in a new tab)
- https://git.kernel.org/stable/c/27ca8004ba93a0665faa6d477eaeb551e03de6c8 (opens in a new tab)
- https://git.kernel.org/stable/c/1d2178918efc928e11bed9631469ef79ff0a862a (opens in a new tab)
- https://git.kernel.org/stable/c/b85758e76b6452740fc2a08ced6759af64c0d59a (opens in a new tab)
- https://git.kernel.org/stable/c/63b7af49496d0e32f7a748b6af3361ec138b1bd3 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-11277 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2024-58096)Record last updated .