net/sched: taprio: always validate TCA_TAPRIO_ATTR_PRIOMAP
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ a3d43c0d56f1b94e74963a2fbadfb70126d92213 · < c37a27a35eadb59286c9092c49c241270c802ae2| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net/sched: taprio: always validate TCA_TAPRIO_ATTR_PRIOMAP
If one TCA_TAPRIO_ATTR_PRIOMAP attribute has been provided, taprio_parse_mqprio_opt() must validate it, or userspace can inject arbitrary data to the kernel, the second time taprio_change() is called.
First call (with valid attributes) sets dev->num_tc to a non zero value.
Second call (with arbitrary mqprio attributes) returns early from taprio_parse_mqprio_opt() and bad things can happen.
From the CVE record · Linux
The Linux kernel's taprio scheduler can fail to validate a supplied TCA_TAPRIO_ATTR_PRIOMAP attribute. After a first taprio_change() call with valid attributes sets dev->num_tc to a nonzero value, a second call from userspace can inject arbitrary data into the kernel. The input does not specify authentication or other access requirements.
Engineers running the Linux kernel should check whether their version is affected; affected versions are not specified.