CVE-2026-93830

net: stmmac: xgmac2: disable RBUE in default RX interrupt mask

HIGH
7.5
CVSS Score
Published: September 24, 2026 at 04:03 PM UTC
Updated: October 3, 2026 at 11:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 0.5%

Description

In the Linux kernel, the following vulnerability has been resolved: net: stmmac: xgmac2: disable RBUE in default RX interrupt mask Enabling the RX Buffer Unavailable (RBUE) interrupt is counterproductive and can trigger a MAC interrupt storm under heavy RX pressure. When the DMA runs out of RX descriptors it fires RBUE continuously until software refills the ring. However, RBUE is redundant: the normal RX completion interrupt (RIE) already triggers NAPI, which processes completed descriptors and refills the ring, causing the DMA to resume. The RBUE handler itself only sets handle_rx - the same outcome as RIE. On Agilex5 under heavy RX pressure, the MAC interrupt (which includes RBUE) was observed firing 1,821,811,555 times against only 2,618,627 actual RX completions - a ~695x ratio - confirming the severity of the storm. RBUE does not provide OOM recovery. If page_pool is exhausted, stmmac_rx_refill() cannot advance the DMA tail pointer, the DMA stays suspended, and RBUE fires again on the next NAPI completion - a storm with no forward progress. This patch trades that storm for a clean stall with the same RX outcome. Proper OOM recovery is a pre-existing gap outside the scope of this fix. Note: as a consequence of disabling RBUE, the rx_buf_unav_irq ethtool counter will always read 0 on XGMAC2 devices. This behaviour is already inconsistent across DWMAC core versions. Remove RBUE from XGMAC_DMA_INT_DEFAULT_EN and XGMAC_DMA_INT_DEFAULT_RX to prevent the interrupt storm while keeping normal RX handling intact.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.19 ≤ v < 5.10.2714.19 ≤ v < 5.15.2224.19 ≤ v < 6.1.1894.19 ≤ v < 6.12.1114.19 ≤ v < 6.18.534.19 ≤ v < 6.6.1584.19 ≤ v < 7.24.19d6ddfacd95c79d43465d4a85dffb1c9beca343a9
Vendor states this is fixed in 0b1a5d3647ce07c27a9fffefc11a8cbf7d7b25ce (fixed)
Vendor states this is fixed in 6b3b91433d5f4eae6865cdaa96f40cd67849e1f6 (fixed)
Vendor states this is fixed in 74dbb85a6a254b5fc1f265a6cd61b2ba9d9221d7 (fixed)
Vendor states this is fixed in 7a10e54e42a8f73a8d731f5a281fc06bb41b9250 (fixed)
Vendor states this is fixed in 87e2826ed2058747ddf014c082569a46bfadd96b (fixed)
Vendor states this is fixed in 8c9d57b5dc098b84631d0b3559c84c499ea2170a (fixed)
Vendor states this is fixed in d3265c19b35d036bba327b36b5366bee76b0157c (fixed)
Vendor states this is fixed in 4.19 (unaffected)
Vendor states this is fixed in 5.10.271 (unaffected)
Vendor states this is fixed in 5.15.222 (unaffected)
Vendor states this is fixed in 6.1.189 (unaffected)
Vendor states this is fixed in 6.12.111 (unaffected)
Vendor states this is fixed in 6.18.53 (unaffected)
Vendor states this is fixed in 6.6.158 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

CVSS

7.5HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card