CVE-2026-63983
Last modified
CVE-2026-63983 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: net/sched: fix packet loop on netem when duplicate is on When netem duplicates a packet it re-enqueues the copy at the root qdisc. If another netem sits in the tree the copy can be duplicated again, recursing until the stack or memory is exhausted. The original duplication guard temporarily zeroed q->duplicate around the re-enqueue, but that does not cover all cases because it is per-qdisc state shared across all concurrent enqueue paths and is not safe without additional locking. Use the skb tc_depth field introduced in an earlier patch: - increment it on the duplicate before re-enqueue - skip duplication for any skb whose tc_depth is already non-zero. This marks the packet itself rather than mutating qdisc state, therefore it is safe regardless of tree topology or concurrency.. EPSS estimates a 0.17% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: net/sched: fix packet loop on netem when duplicate is on When netem duplicates a packet it re-enqueues the copy at the root qdisc. If another netem sits in the tree the copy can be duplicated again, recursing until the stack or memory is exhausted. The original duplication guard temporarily zeroed q->duplicate around the re-enqueue, but that does not cover all cases because it is per-qdisc state shared across all concurrent enqueue paths and is not safe without additional locking. Use the skb tc_depth field introduced in an earlier patch: - increment it on the duplicate before re-enqueue - skip duplication for any skb whose tc_depth is already non-zero. This marks the packet itself rather than mutating qdisc state, therefore it is safe regardless of tree topology or concurrency.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 0afb51e72855971dba83b3c6b70c547c2d1161fd, < 1a298a514ce766c6d0c232991a390fec67af81ad; >= 0afb51e72855971dba83b3c6b70c547c2d1161fd, < cfb2616042767ab31260d4f39190c381bec8b12e; >= 0afb51e72855971dba83b3c6b70c547c2d1161fd, < 9552b11e3edabc97cfcd9f29103d5afbce7ae183 |
| Linux | Linux | 2.6.12 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-63983?
How severe is CVE-2026-63983?
How do I fix CVE-2026-63983?
How Strix Helps
- 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.
Related CVEs from 2026
- CVE-2026-63978In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-63979In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-6398Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMB…
- CVE-2026-63980In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-63981In the Linux kernel, the following vulnerability has been re…
- CVE-2026-63982In the Linux kernel, the following vulnerability has been re…
- CVE-2026-63984In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-63985In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-63986In the Linux kernel, the following vulnerability has been re…
- CVE-2026-63987In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-63988In the Linux kernel, the following vulnerability has been re…
- CVE-2026-63989In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-63983?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
