wifi: ath11k: fix RCU stall while reaping monitor destination ring (CVE-2024-58097) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2024-58097

wifi: ath11k: fix RCU stall while reaping monitor destination ring

Answer in brief

CVE-2024-58097 records a Unknown severity vulnerability in wifi: ath11k: fix RCU stall while reaping monitor destination ring. The current sources do not mark it as known exploited. The current feed maps 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.

Published Apr 16, 2025Updated Sep 14, 2026Source checked Sep 14, 2026First seen by HOL Sep 14, 2026Material review Sep 14, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. 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.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=d5c65159f2895379e11ca13f62feabe93278985d <cdb32923699932502b0573f818643aae72ce0cd5 \|\| >=d5c65159f2895379e11ca13f62feabe93278985d <8db5de0cf02fccf4c759aa58edbe65659daf607c \|\| >=d5c65159f2895379e11ca13f62feabe93278985d <9f1a002f0171d27f3554e529f3c70df438f05dfe \|\| >=d5c65159f2895379e11ca13f62feabe93278985d <b4991fc41745645f8050506f5a8578bd11e6b378 \|\| >=d5c65159f2895379e11ca13f62feabe93278985d <16c6c35c03ea73054a1f6d3302a4ce4a331b427d	cdb32923699932502b0573f818643aae72ce0cd5, 8db5de0cf02fccf4c759aa58edbe65659daf607c, 9f1a002f0171d27f3554e529f3c70df438f05dfe, b4991fc41745645f8050506f5a8578bd11e6b378, 16c6c35c03ea73054a1f6d3302a4ce4a331b427d
Linux/Linuxgeneric	5.6	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to cdb32923699932502b0573f818643aae72ce0cd5 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Apr 16, 2025
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 14, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 14, 2026

Sources and claim methodology

Upstream source description

In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: fix RCU stall while reaping monitor destination ring While processing the monitor destination ring, MSDUs are reaped from the link descriptor based on the corresponding buf_id. However, sometimes the driver cannot obtain a valid buffer corresponding to the buf_id received from the hardware. This causes an infinite loop in the destination processing, resulting in a kernel crash. kernel log: ath11k_pci 0000:58:00.0: data msdu_pop: invalid buf_id 309 ath11k_pci 0000:58:00.0: data dp_rx_monitor_link_desc_return failed ath11k_pci 0000:58:00.0: data msdu_pop: invalid buf_id 309 ath11k_pci 0000:58:00.0: data dp_rx_monitor_link_desc_return failed Fix this by skipping the problematic buf_id and reaping the next entry, replacing the break with the next MSDU processing. 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

Quoted source text, attributed separately from HOL analysis.