VulnerabilityPublished 19 Jul 2026

CVE-2026-63982: Linux kernel · net/sched: Fix ethx:ingress -> ethy:egress -> ethx:ingress mirred loop

Source GCVE Database

Not known to be exploited.

Data as of 26 Oct 2026, 14:05 UTC

Severity

Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-g6rc-cvjj-cfmj

What to do

AI-suggested

A fix for this vulnerability has been implemented in the Linux kernel. Users should apply the official kernel updates that include this fix. Since no vendor advisory or patch links are provided, check the Linux kernel mailing lists or official repositories for the specific patch or updated kernel versions. No additional mitigation actions are indicated.

Description

A vulnerability in the Linux kernel's network scheduler (net/sched) involving mirred redirect loops between ingress and egress interfaces has been resolved. The issue occurs because the loop detection state is lost due to packet deferral and clearing of the sched_mirred_dev array, preventing discovery of mirred loops. This can cause unexpected network behavior when mirred actions redirect packets between interfaces in a loop. A test case demonstrates the loop creation using traffic control commands and ping. No CVSS score is available for this vulnerability.

Impact

The vulnerability causes the kernel to fail to detect mirred redirect loops between network interfaces, potentially resulting in network packet loops. This can degrade network performance or cause unexpected network behavior. There is no indication of remote code execution or privilege escalation from the provided data.

Summary

The Linux kernel vulnerability CVE-2026-63982 involves the net/sched subsystem where mirred redirect actions create a loop between ingress and egress interfaces (ethx:ingress -> ethy:egress -> ethx:ingress). The loop detection state stored in the sched_mirred_dev array is lost due to packet deferral into the backlog and clearing of this array, causing the kernel to fail to detect the loop. This can lead to network packet processing loops that may impact network functionality. The issue has been resolved in the Linux kernel.

References

Community reviews

Loading reviews…