A divide-by-zero vulnerability was identified and resolved in the Linux kernel's IPv4 fib_rebalance function. The issue occurs when concurrent changes cause the first pass of nexthop weight calculation to return zero, while the second pass still sees eligible nexthops, leading to division by zero. The fix sets nexthop upper bounds to -1 when the total is zero, avoiding the division and aligning with a similar IPv6 fix.