net_sched: red: fix a race in __red_change()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 0c8d13ac96070000da33f394f45e9c19638483c5 · < 4b755305b2b0618e857fdadb499365b5f2e478d1| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net_sched: red: fix a race in __red_change()
Gerrard Tai reported a race condition in RED, whenever SFQ perturb timer fires at the wrong time.
The race is as follows:
CPU 0 CPU 1 [1]: lock root [2]: qdisc_tree_flush_backlog() [3]: unlock root | | [5]: lock root | [6]: rehash | [7]: qdisc_tree_reduce_backlog() | [4]: qdisc_put()
This can be abused to underflow a parent's qlen.
Calling qdisc_purge_queue() instead of qdisc_tree_flush_backlog() should fix the race, because all packets will be purged from the qdisc before releasing the lock.
From the CVE record · Linux
A race in the Linux kernel's RED network scheduler can occur when the SFQ perturb timer fires during a RED change. It can be abused to underflow a parent queue's length. The input does not specify the access or authentication needed to trigger it.
Engineers running the Linux kernel should check affected versions; the input does not identify specific versions.