Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2024-58096 — kernel

🟠 CVSS 8.8 — High ✅ No Known Exploit NVD
8.8
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

wifi: ath11k: add srng->lock for ath11k_hal_srng_* in monitor mode

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

How this vulnerability can be exploited

This issue can be reached from an adjacent network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity high, availability high.

Affected software

CVE-2024-58096 is recorded against 2 packages.

  • kernel (from 6.13.0 up to 6.14.2)
  • linux-kernel (from 5.6 up to 6.14.2)

Timeline and source

Published on 16 April 2025 and last revised on 12 August 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
github.com (Advisory)
nvd.nist.gov (Advisory)
git.kernel.org (Package)

CVE-2024-58096 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Severity High
CVSS Score 8.8
CVSS Vector CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CWE N/A
Public Exploit ✅ No
Source NVD
Published 2025-04-16
Updated 2026-08-20
Modified 2026-08-12

Affected Packages

Software From version Fixed in
kernel 6.13.0 6.14.2
linux-kernel 5.6 6.14.2

Similar Threats

Site Security Check

Is kernel part of your stack?

CVE-2024-58096 is rated CVSS 8.8 High. BotEraser scans your installation against known CVE records and tells you whether this vulnerability applies to the versions you actually run.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.