Description
In the Linux kernel, the following vulnerability has been resolved: net/sched: act_mirred: use the backlog for mirred ingress The test Davide added in commit ca22da2fbd69 ("act_mirred: use the backlog for nested calls to mirred ingress") hangs our testing VMs every 10 or so runs, with the familiar tcp_v4_rcv -> tcp_v4_rcv deadlock reported by lockdep. The problem as previously described by Davide (see Link) is that if we reverse flow of traffic with the redirect (egress -> ingress) we may reach the same socket which generated the packet. And we may still be holding its socket lock. The common solution to such deadlocks is to put the packet in the Rx backlog, rather than run the Rx path inline. Do that for all egress -> ingress reversals, not just once we started to nest mirred calls. In the past there was a concern that the backlog indirection will lead to loss of error reporting / less accurate stats. But the current workaround does not seem to address the issue.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
53592b3640019f2834701093e38272fdfd367ad8 to < ac5c2ed6394c85f84877b1a1eec61cf004f90f4faffected53592b3640019f2834701093e38272fdfd367ad8 to < 7c787888d164689da8b1b115f3ef562c1e843af4affected53592b3640019f2834701093e38272fdfd367ad8 to < 60ddea1600bc476e0f5e02bce0e29a460ccbf0beaffected53592b3640019f2834701093e38272fdfd367ad8 to < 52f671db18823089a02f07efc04efdb2272ddc17affected
Linux Linux
Default version status: affected
4.10affected0 to < 4.10unaffected6.1.191 to ≤ 6.1.*unaffected6.6.19 to ≤ 6.6.*unaffected6.7.7 to ≤ 6.7.*unaffected6.8 to ≤ *unaffected