CVE-2026-43371

In the Linux kernel, the following vulnerability has been resolved: net: macb: Shuffle the tx ring before enabling tx Quanyang observed that when using an NFS rootfs on an AMD ZynqMp board, the rootfs may take an extended time to recover after a suspend. Upon investigation, it was determined that the issue originates from a problem in the macb driver. According to the Zynq UltraScale TRM [1], when transmit is disabled, the transmit buffer queue pointer resets to point to the address specified by the transmit buffer queue base address register. In the current implementation, the code merely resets `queue->tx_head` and `queue->tx_tail` to '0'. This approach presents several issues: - Packets already queued in the tx ring are silently lost, leading to memory leaks since the associated skbs cannot be released. - Concurrent write access to `queue->tx_head` and `queue->tx_tail` may occur from `macb_tx_poll()` or `macb_start_xmit()` when these values are reset to '0'. - The transmission may become stuck on a packet that has already been sent out, with its 'TX_USED' bit set, but has not yet been processed. However, due to the manipulation of 'queue->tx_head' and 'queue->tx_tail', `macb_tx_poll()` incorrectly assumes there are no packets to handle because `queue->tx_head == queue->tx_tail`. This issue is only resolved when a new packet is placed at this position. This is the root cause of the prolonged recovery time observed for the NFS root filesystem. To resolve this issue, shuffle the tx ring and tx skb array so that the first unsent packet is positioned at the start of the tx ring. Additionally, ensure that updates to `queue->tx_head` and `queue->tx_tail` are properly protected with the appropriate lock. [1] https://docs.amd.com/v/u/en-US/ug1085-zynq-ultrascale-trm

• CWE-401

• https://git.kernel.org/stable/c/0a47c3889fcd843c72aa57fa8c4d06f5801fced4Patch
• https://git.kernel.org/stable/c/403182e0771b250cfde0fe7e1081d095ceaf8230Patch
• https://git.kernel.org/stable/c/58f5d34f88e8f00910b692537f7b2efdb8c3705dPatch
• https://git.kernel.org/stable/c/881a0263d502e1a93ebc13a78254e9ad19520232Patch
• https://git.kernel.org/stable/c/88f974fe118cb4653f029929ecbca7cfe06132aePatch
• https://git.kernel.org/stable/c/c6783bfa31a59f34fe4feb1bdbf67791ef3fb0b7Patch

Published

May 8, 2026

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-2026-43365In the Linux kernel, the following vulnerability has been re…8.2
• CVE-2026-43366In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-43367In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-43368In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-43369In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-43370In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-43372In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-43373In the Linux kernel, the following vulnerability has been re…7.5
• CVE-2026-43374In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-43375In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-43376In the Linux kernel, the following vulnerability has been re…9.8
• CVE-2026-43377In the Linux kernel, the following vulnerability has been re…8.1