net/sched: sch_taprio: Replace direct dequeue call with peek and qdisc_dequeue_peeked
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 5a781ccbd19e4664babcbe4b4ead7aa2b9283d22 · < e2b7ee61989f2d39df6c2cc06f9db1aea69bdb09| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
In the Linux kernel, taprio's software path can mishandle a packet peeked from a non-work-conserving child queue. With a qfq child, ordinary egress traffic can trigger a NULL dereference and panic the kernel. The input does not specify attacker access or authentication requirements.
Operators running Linux kernels that use taprio's software path with a non-work-conserving child queue should check their kernel's advisory; affected versions are not specified.