CVE-2026-72035
HighCVSS 8.2Exploitation Probability (EPSS)
Low risk43th percentile - higher than 43% of all known CVEs
Summary
In the Linux kernel network scheduler sch_taprio, a vulnerability exists due to direct dequeue call instead of using peek and qdisc_dequeue_peeked. When the child is non-work-conserving, direct dequeue can lead to qlen/backlog desync and potential kernel panic.
Risk Assessment
This could lead to kernel panic during normal network traffic, especially in configurations with qfq.
Recommendation
Apply a kernel update containing the fix that uses qdisc_dequeue_peeked() instead of direct dequeue call.
Original NVD description (English source)
In the Linux kernel, the following vulnerability has been resolved: net/sched: sch_taprio: Replace direct dequeue call with peek and qdisc_dequeue_peeked When taprio's software path peeks a non-work-conserving child qdisc, the child stashes the peeked skb in its gso_skb; taprio_dequeue_from_txq() then takes the packet with a direct child ->dequeue() call, which ignores that stash, orphans the peeked skb and desyncs the child's qlen/backlog. With a qfq child this re-enters the child on an emptied list and dereferences NULL, panicking the kernel from softirq on ordinary egress. Take the packet through qdisc_dequeue_peeked(), as sch_red and sch_sfb now do. The helper returns the child's stashed skb first and is a no-op when there is none, so a work-conserving child is unaffected and the gated path now consumes the skb whose length was charged to the budget.