---
id: CVE-2024-58096
title: |-
  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_pr…
summary: |-
  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_pr…
severity: high
cvss: 8.8
cvssVector: 'CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'
vendor: linux
product: linux_kernel
affected:
  - 'linux_kernel >= 5.6, < 6.14.2'
patched:
  - linux_kernel 6.14.2
published: '2025-04-16'
updated: '2026-10-15'
sourceUpdated: '2026-10-15T22:18:05.617'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2024-58096'
references:
  - url: 'https://git.kernel.org/stable/c/1d2178918efc928e11bed9631469ef79ff0a862a'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/27ca8004ba93a0665faa6d477eaeb551e03de6c8'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/63b7af49496d0e32f7a748b6af3361ec138b1bd3'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/b85758e76b6452740fc2a08ced6759af64c0d59a'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/b7cc16629ae391c8ba44464ca29fcbbc1a3e1336'
tags:
  - nvd
  - cve.org
epss: 0.0025
epssPercentile: 0.16269
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: total
  timestamp: '2026-10-15T21:42:16.330422Z'
ingestedAt: '2026-10-15T22:48:25.466Z'
---

## Overview

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

## Affected

- `linux_kernel >= 5.6, < 6.14.2`

## Remediation

Upgrade past the affected range:

- `linux_kernel 6.14.2`