net_sched: sch_sfq: fix a potential crash on gso_skb handling
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ a53851e2c3218aa30b77abd6e68cf1c371f15afe · < d1bc80da75c789f2f6830df89d91fb2f7a509943| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net_sched: sch_sfq: fix a potential crash on gso_skb handling
SFQ has an assumption of always being able to queue at least one packet.
However, after the blamed commit, sch->q.len can be inflated by packets in sch->gso_skb, and an enqueue() on an empty SFQ qdisc can be followed by an immediate drop.
Fix sfq_drop() to properly clear q->tail in this situation.
ip netns add lb ip link add dev to-lb type veth peer name in-lb netns lb ethtool -K to-lb tso off # force qdisc to requeue gso_skb ip netns exec lb ethtool -K in-lb gro on # enable NAPI ip link set dev to-lb up ip -netns lb link set dev in-lb up ip addr add dev to-lb 192.168.20.1/24 ip -netns lb addr add dev in-lb 192.168.20.2/24 tc qdisc replace dev to-lb root sfq limit 100
ip netns exec lb netserver
netperf -H 192.168.20.2 -l 100 & netperf -H 192.168.20.2 -l 100 & netperf -H 192.168.20.2 -l 100 & netperf -H 192.168.20.2 -l 100 &
From the CVE record · Linux
The Linux kernel’s SFQ packet scheduler can crash when packets in its GSO queue inflate the reported queue length and an enqueue on an empty SFQ queue is immediately dropped. The input does not establish whether an attacker can trigger this remotely or locally, whether authentication is required, or whether user interaction is needed.
Engineers running Linux kernels that use the SFQ packet scheduler should check their systems; affected versions are not specified.