net/sched: Fix mirred deadlock on device recursion
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 09d2e807aeb8e4f2e5eac4a3064f28dcf19b9c1e, Kernel 0f022d32c3eca477fbf79a205243a6123ed0fe11, Kernel 524323f52cbfbac4fe3f8a33a8cc405fafba0d33 and 1 more.
In the Linux kernel, the following vulnerability has been resolved: net/sched: Fix mirred deadlock on device recursion When the mirred action is used on a classful egress qdisc and a packet is mirrored or redirected to self we hit a qdisc lock deadlock. See trace below. [..... other info removed for brevity....] [ 82.890906] [ 82.890906] ============================================ [ 82.890906] WARNING: possible recursive locking detected [ 82.890906] 6.8.0-05205-g77fadd89fe2d-dirty #213 Tainted: G W [ 82.890906] -------------------------------------------- [ 82.890906] ping/418 is trying to acquire lock: [ 82.890906] ffff888006994110 (&sch->q.lock){+.-.}-{3:3}, at: __dev_queue_xmit+0x1778/0x3550 [ 82.890906] [ 82.890906] but task is already holding lock: [ 82.890906] ffff888006994110 (&sch->q.lock){+.-.}-{3:3}, at: __dev_queue_xmit+0x1778/0x3550 [ 82.890906] [ 82.890906] other info that might help us debug this: [ 82.890906] Possible unsafe locking scenario: [ 82.890906] [ 82.890906] CPU0 [ 82.890906] ---- [ 82.890906] lock(&sch->q.lock); [ 82.890906] lock(&sch->q.lock); [ 82.890906] [ 82.890906] *** DEADLOCK *** [ 82.890906] [..... other info removed for brevity....] Example setup (eth0->eth0) to recreate tc qdisc add dev eth0 root handle 1: htb default 30 tc filter add dev eth0 handle 1: protocol ip prio 2 matchall \ action mirred egress redirect dev eth0 Another example(eth0->eth1->eth0) to recreate tc qdisc add dev eth0 root handle 1: htb default 30 tc filter add dev eth0 handle 1: protocol ip prio 2 matchall \ action mirred egress redirect dev eth1 tc qdisc add dev eth1 root handle 1: htb default 30 tc filter add dev eth1 handle 1: protocol ip prio 2 matchall \ action mirred egress redirect dev eth0 We fix this by adding an owner field (CPU id) to struct Qdisc set after root qdisc is entered. When the softirq enters it a second time, if the qdisc owner is the same CPU, the packet is dropped to break the loop.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =4.2, >=e578d9c02587d57bfa7b560767c698a668a468c6 <09d2e807aeb8e4f2e5eac4a3064f28dcf19b9c1e, >=e578d9c02587d57bfa7b560767c698a668a468c6 <0f022d32c3eca477fbf79a205243a6123ed0fe11, >=e578d9c02587d57bfa7b560767c698a668a468c6 <524323f52cbfbac4fe3f8a33a8cc405fafba0d33, >=e578d9c02587d57bfa7b560767c698a668a468c6 <e6b90468da4dae2281a6e381107f411efb48b0ef | 09d2e807aeb8e4f2e5eac4a3064f28dcf19b9c1e, 0f022d32c3eca477fbf79a205243a6123ed0fe11, 524323f52cbfbac4fe3f8a33a8cc405fafba0d33, e6b90468da4dae2281a6e381107f411efb48b0ef |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket