CVE-2023-52611

In the Linux kernel, the following vulnerability has been resolved: wifi: rtw88: sdio: Honor the host max_req_size in the RX path Lukas reports skb_over_panic errors on his Banana Pi BPI-CM4 which comes with an Amlogic A311D (G12B) SoC and a RTL8822CS SDIO wifi/Bluetooth combo card. The error he observed is identical to what has been fixed in commit e967229ead0e ("wifi: rtw88: sdio: Check the HISR RX_REQUEST bit in rtw_sdio_rx_isr()") but that commit didn't fix Lukas' problem. Lukas found that disabling or limiting RX aggregation works around the problem for some time (but does not fully fix it). In the following discussion a few key topics have been discussed which have an impact on this problem: - The Amlogic A311D (G12B) SoC has a hardware bug in the SDIO controller which prevents DMA transfers. Instead all transfers need to go through the controller SRAM which limits transfers to 1536 bytes - rtw88 chips don't split incoming (RX) packets, so if a big packet is received this is forwarded to the host in it's original form - rtw88 chips can do RX aggregation, meaning more multiple incoming packets can be pulled by the host from the card with one MMC/SDIO transfer. This Depends on settings in the REG_RXDMA_AGG_PG_TH register (BIT_RXDMA_AGG_PG_TH limits the number of packets that will be aggregated, BIT_DMA_AGG_TO_V1 configures a timeout for aggregation and BIT_EN_PRE_CALC makes the chip honor the limits more effectively) Use multiple consecutive reads in rtw_sdio_read_port() and limit the number of bytes which are copied by the host from the card in one MMC/SDIO transfer. This allows receiving a buffer that's larger than the hosts max_req_size (number of bytes which can be transferred in one MMC/SDIO transfer). As a result of this the skb_over_panic error is gone as the rtw88 driver is now able to receive more than 1536 bytes from the card (either because the incoming packet is larger than that or because multiple packets have been aggregated). In case of an receive errors (-EILSEQ has been observed by Lukas) we need to drain the remaining data from the card's buffer, otherwise the card will return corrupt data for the next rtw_sdio_read_port() call.

• https://git.kernel.org/stable/c/00384f565a91c08c4bedae167f749b093d10e3feMailing List, Patch
• https://git.kernel.org/stable/c/0e9ffff72a0674cd6656314dbd99cdd2123a3030Mailing List, Patch
• https://git.kernel.org/stable/c/5b5ddf21b978ec315cab9d9e7e6ac7374791a8c7Mailing List, Patch
• https://git.kernel.org/stable/c/00384f565a91c08c4bedae167f749b093d10e3feMailing List, Patch
• https://git.kernel.org/stable/c/0e9ffff72a0674cd6656314dbd99cdd2123a3030Mailing List, Patch
• https://git.kernel.org/stable/c/5b5ddf21b978ec315cab9d9e7e6ac7374791a8c7Mailing List, Patch

Published

Mar 18, 2024

Last Modified

Jun 17, 2026

Status

Analyzed

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2023-52606In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2023-52607In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2023-52608In the Linux kernel, the following vulnerability has been re…4.7
• CVE-2023-52609In the Linux kernel, the following vulnerability has been re…4.7
• CVE-2023-5261A vulnerability, which was classified as critical, was found…9.8
• CVE-2023-52610In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2023-52612In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2023-52613In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2023-52614In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2023-52615In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2023-52616In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2023-52617In the Linux kernel, the following vulnerability has been re…4.4