net_sched: skbprio: Remove overly strict queue assertions
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ aea5f654e6b78a0c976f7a25950155932c77a53f · < 2f35b7673a3aa3d09b3eb05811669622ebaa98ca| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net_sched: skbprio: Remove overly strict queue assertions
In the current implementation, skbprio enqueue/dequeue contains an assertion that fails under certain conditions when SKBPRIO is used as a child qdisc under TBF with specific parameters. The failure occurs because TBF sometimes peeks at packets in the child qdisc without actually dequeuing them when tokens are unavailable.
This peek operation creates a discrepancy between the parent and child qdisc queue length counters. When TBF later receives a high-priority packet, SKBPRIO's queue length may show a different value than what's reflected in its internal priority queue tracking, triggering the assertion.
The fix removes this overly strict assertions in SKBPRIO, they are not necessary at all.
From the CVE record · Linux
An overly strict assertion in the Linux kernel’s SKBPRIO queueing discipline can fail when SKBPRIO is used as a child of TBF with specific parameters. TBF may peek at packets without dequeuing them when tokens are unavailable, creating a queue-length discrepancy that triggers the assertion when a high-priority packet arrives. The input does not specify attacker access requirements or user interaction.
Operators running Linux kernels that use SKBPRIO as a child qdisc under TBF should check their affected versions; none are specified in the input.