ipv4: Avoid crashing in ip_error
ip_error does not check if in_dev is NULL before dereferencing it.
IThe following sequence of calls is possible:
CPU A CPU B
With the result that a network device can be destroyed while processing
an input packet.
A crash was triggered with only unicast packets in flight, and
forwarding enabled on the only network device. The error condition
was created by the removal of the network device.
As such it is likely the that error code was -EHOSTUNREACH, and the
action taken by ip_error (if in_dev had been accessible) would have
been to not increment any counters and to have tried and likely failed
to send an icmp error as the network device is going away.
Therefore handle this weird case by just dropping the packet if
!in_dev. It will result in dropping the packet sooner, and will not
result in an actual change of behavior.
Fixes: 251da4130115b ("ipv4: Cache ip_error() routes even when not forwarding.")
Reported-by: Vittorio Gambaletta <email@example.com>
Tested-by: Vittorio Gambaletta <firstname.lastname@example.org>
Signed-off-by: Vittorio Gambaletta <email@example.com>
Signed-off-by: "Eric W. Biederman" <firstname.lastname@example.org>
Acked-by: Eric Dumazet <email@example.com>
Signed-off-by: David S. Miller <firstname.lastname@example.org>
1 file changed