CVE-2026-43371

MEDIUM EPSS 2.4%
Published May 8, 20261mo ago · Modified Jun 17, 20261w ago
5.5 CVSS 3.1
Medium
Find Similar
Published May 8, 2026 1mo ago
Last Modified Jun 17, 2026 1w ago

Description

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

CVSS Details

Base Score
5.5
Exploitability
1.8
Impact
3.6
Vector string
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Attack Vector Local
Attack Complexity Low
Privileges Required Low
User Interaction None
Scope Unchanged
Confidentiality None
Integrity None
Availability High

Threat Intelligence

EPSS Exploit Probability
2.4% percentile
Exploit & Patch Status
No Known Exploit
Patch Available

Weaknesses 1

CWE-401

Affected Products 5

VendorProductVersionRange
linuxlinux_kernel*≥6.1.165  –  <6.1.167
linuxlinux_kernel*≥6.6.128  –  <6.6.130
linuxlinux_kernel*≥6.12.75  –  <6.12.78
linuxlinux_kernel*≥6.18.16  –  <6.18.20
linuxlinux_kernel*≥6.19.6  –  <6.19.9

References 6

  • git.kernel.org https://git.kernel.org/stable/c/0a47c3889fcd843c72aa57fa8c4d06f5801fced4
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/403182e0771b250cfde0fe7e1081d095ceaf8230
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/58f5d34f88e8f00910b692537f7b2efdb8c3705d
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/881a0263d502e1a93ebc13a78254e9ad19520232
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/88f974fe118cb4653f029929ecbca7cfe06132ae
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/c6783bfa31a59f34fe4feb1bdbf67791ef3fb0b7
    Patch

Remediation

  • git.kernel.org https://git.kernel.org/stable/c/0a47c3889fcd843c72aa57fa8c4d06f5801fced4
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/403182e0771b250cfde0fe7e1081d095ceaf8230
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/58f5d34f88e8f00910b692537f7b2efdb8c3705d
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/881a0263d502e1a93ebc13a78254e9ad19520232
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/88f974fe118cb4653f029929ecbca7cfe06132ae
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/c6783bfa31a59f34fe4feb1bdbf67791ef3fb0b7
    Patch