net/sched: sch_api: fix xa_insert() error path in tcf_block_get_ext()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net/sched: sch_api: fix xa_insert() error path in tcf_block_get_ext()
This command:
$ tc qdisc replace dev eth0 ingress_block 1 egress_block 1 clsact Error: block dev insert failed: -EBUSY.
fails because user space requests the same block index to be set for both ingress and egress.
[ side note, I don't think it even failed prior to commit 913b47d3424e ("net/sched: Introduce tc block netdev tracking infra"), because this is a command from an old set of notes of mine which used to work, but alas, I did not scientifically bisect this ]
The problem is not that it fails, but rather, that the second time around, it fails differently (and irrecoverably):
$ tc qdisc replace dev eth0 ingress_block 1 egress_block 1 clsact Error: dsa_core: Flow block cb is busy.
From the CVE record · Linux
The Linux kernel’s traffic-control block setup fails to undo an offload binding when inserting a device into a block fails. A local user issuing a tc command that assigns the same block index to ingress and egress can leave the device’s flow-block callback busy, preventing subsequent configuration until the system is rebooted or the network driver is unbound and rebound; the input does not specify authentication requirements.
Engineers running Linux kernels with the affected net/sched code should check their kernel vendor’s advisory; affected versions were not provided.