net/sched: sch_multiq: 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 |
|
≥ 77be155cba4e163e8bba9fd27222a8b6189ec4f7 · < 5889064919a1e5c0a9469c54895000414fc46944| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net/sched: sch_multiq: Replace direct dequeue call with peek and qdisc_dequeue_peeked
multiq_dequeue() takes a packet from a band's child with a direct ->dequeue() call after multiq_peek() peeked it. When the child is non-work-conserving the peek stashes the skb in the child's gso_skb, so the direct dequeue returns a different skb and orphans the stash, desyncing the child's qlen/backlog. With a qfq child reached through a peeking parent (e.g. tbf) 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_prio already does and as sch_red and sch_sfb were just fixed to do. The helper is a no-op when the child has no stash, so a work-conserving child is unaffected.
From the CVE record · Linux
The Linux kernel's multiq scheduler can mishandle a packet when a non-work-conserving child queue has stashed it during a peek. With a qfq child reached through a peeking parent such as tbf, ordinary egress can then trigger a NULL dereference and kernel panic. The input does not specify authentication requirements or whether user interaction is needed.
Engineers running Linux kernels with multiq and the affected child-queue configuration should check their deployments; affected versions are not specified.