CVE-2026-63982

net/sched: Fix ethx:ingress -> ethy:egress -> ethx:ingress mirred loop

Published Jul 19, 2026 CVSS 3.1 · 5.5 Medium EPSS < 1% KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

net/sched: Fix ethx:ingress -> ethy:egress -> ethx:ingress mirred loop

When mirred redirects to ingress (from either ingress or egress) the loop
state from sched_mirred_dev array dev is lost because of 1) the packet
deferral into the backlog and 2) the fact the sched_mirred_dev array is
cleared. In such cases, if there was a loop we won't discover it.

Here's a simple test to reproduce:
ip a add dev port0 10.10.10.11/24

tc qdisc add dev port0 clsact
tc filter add dev port0 egress protocol ip \
prio 10 matchall action mirred ingress redirect dev port1

tc qdisc add dev port1 clsact
tc filter add dev port1 ingress protocol ip \
prio 10 matchall action mirred egress redirect dev port0

ping -c 1 -W0.01 10.10.10.10

Analysis

AI-generated

Technical impact

A fault in the Linux kernel networking scheduler caused the loop‑detection logic for mirred (mirror) redirects to fail when a packet is redirected from ingress or egress to another device and back. The bookkeeping array that records in‑flight mirred operations is cleared unexpectedly, so a looping configuration is not detected. This flaw results in packets continuing to be processed indefinitely, potentially exhausting kernel resources or causing kernel stalls. The vulnerability is purely functional and does not provide code execution or privilege escalation. It is associated with CWE‑835 (Resource Exhaustion).

Affected Systems

All Linux kernel builds older than the commit that introduced the mirred loop‑tracking fix. The issue resides in the core networking scheduler and affects any distribution that has not incorporated the upstream patch. No specific versions are listed in the CVE payload, so any kernel version before the fix remains vulnerable.

Risk and Exploitability

The EPSS score is reported as less than 1%, indicating a very low likelihood of exploitation, and the vulnerability is not listed in CISA’s KEV database. An attacker would need to craft network traffic that activates a mirred mirroring loop across two devices, which requires precise configuration of mirred filters on the involved interfaces. This limits the practical attack surface, but if the loop were triggered it could lead to denial of service by exhausting kernel resources or pausing the networking stack.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Linux kernel to a release that includes the mirred loop tracking fix
  • Reconfigure or remove any mirred filters that create loops between devices
  • Monitor system performance for packet backlog or kernel resource exhaustion to detect unintended loops

Generated by OpenCVE AI on November 15, 2026 at 12:45 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-8593-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8603-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8618-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8663-1 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-8664-1 Linux kernel (NVIDIA BaseOS) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-1 Linux kernel (GCP) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-2 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-3 Linux kernel (Oracle) vulnerabilities
History
Type Values Removed Values Added
Weaknesses NVD-CWE-noinfo
CPEs cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.1:rc3:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.1:rc4:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.1:rc5:*:*:*:*:*:*
Type Values Removed Values Added
Weaknesses CWE-673
Type Values Removed Values Added
Weaknesses CWE-835
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Low

Type Values Removed Values Added
Weaknesses CWE-673
Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: net/sched: Fix ethx:ingress -> ethy:egress -> ethx:ingress mirred loop When mirred redirects to ingress (from either ingress or egress) the loop state from sched_mirred_dev array dev is lost because of 1) the packet deferral into the backlog and 2) the fact the sched_mirred_dev array is cleared. In such cases, if there was a loop we won't discover it. Here's a simple test to reproduce: ip a add dev port0 10.10.10.11/24 tc qdisc add dev port0 clsact tc filter add dev port0 egress protocol ip \ prio 10 matchall action mirred ingress redirect dev port1 tc qdisc add dev port1 clsact tc filter add dev port1 ingress protocol ip \ prio 10 matchall action mirred egress redirect dev port0 ping -c 1 -W0.01 10.10.10.10
Title net/sched: Fix ethx:ingress -> ethy:egress -> ethx:ingress mirred loop
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Jul 19, 2026, 2:56 PM
Reserved
Jul 19, 2026, 7:54 AM
Status
Analyzed
Published
Jul 19, 2026, 4:17 PM
Modified
Nov 12, 2026, 5:37 PM
Severity
Low
Public date
Jul 19, 2026, 12:00 AM