CVE-2024-58097

What it actually does

Local processing of the ath11k monitor destination ring enters an infinite loop when an invalid buf_id is received from hardware, causing an RCU stall and kernel panic.

Why it matters to the business

Systems using affected Red Hat Enterprise Linux 8.4 kernels with ath11k Wi-Fi hardware can experience sudden crashes and loss of service; widespread kernel package exposure increases operational risk for organizations relying on these distributions.

How an attack unfolds

An attacker with local access triggers repeated monitor ring processing on ath11k hardware by sending crafted frames or operating under conditions that produce invalid buf_ids; the driver fails to skip the bad entry and loops indefinitely until the kernel crashes.

How to fix it

Upgrade all listed Red Hat rhel_aus:8.4 kernel packages to version 0:4.18.0-305.145.1.el8_4 or later; reboot after installation and verify the running kernel matches the fixed release.

How to confirm the fix worked

Confirm the installed kernel version is at least 0:4.18.0-305.145.1.el8_4, reproduce monitor ring processing under load, and ensure the log messages containing 'invalid buf_id' and 'dp_rx_monitor_link_desc_return failed' no longer appear.

Typical attack path

1. Obtain local access to a system running an affected ath11k kernel
2. Trigger monitor destination ring activity via wireless traffic or driver state
3. Supply or induce an invalid buf_id from hardware
4. Driver enters infinite loop during msdu_pop and link descriptor return
5. RCU stall leads to kernel panic and system reboot or hang

How to detect it

Search kernel logs and dmesg for repeated occurrences of 'ath11k_pci' messages containing 'invalid buf_id' followed by 'dp_rx_monitor_link_desc_return failed'; correlate with system crashes or RCU stall reports in the same timeframe.

• ath11k_pci.*data msdu_pop: invalid buf_id
• ath11k_pci.*data dp_rx_monitor_link_desc_return failed

What your security team should do

• Apply the fixed kernel packages immediately on all rhel_aus:8.4 systems containing ath11k hardware
• Prioritize patching internet-facing or high-availability systems first
• Monitor kernel logs for the specific invalid buf_id error strings until patches are deployed
• Plan staged rollouts and test wireless functionality post-upgrade