diff options
author | JianJhen Chen <kchen@synology.com> | 2019-01-06 04:28:13 +0100 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2019-01-07 18:09:02 +0100 |
commit | 4c84edc11b76590859b1e45dd676074c59602dc4 (patch) | |
tree | e0f06b0072608a1a55800a50e5dab17526fdc9d5 /net/bridge/br_stp_if.c | |
parent | tipc: fix memory leak in tipc_nl_compat_publ_dump (diff) | |
download | linux-4c84edc11b76590859b1e45dd676074c59602dc4.tar.xz linux-4c84edc11b76590859b1e45dd676074c59602dc4.zip |
net: bridge: fix a bug on using a neighbour cache entry without checking its state
When handling DNAT'ed packets on a bridge device, the neighbour cache entry
from lookup was used without checking its state. It means that a cache entry
in the NUD_STALE state will be used directly instead of entering the NUD_DELAY
state to confirm the reachability of the neighbor.
This problem becomes worse after commit 2724680bceee ("neigh: Keep neighbour
cache entries if number of them is small enough."), since all neighbour cache
entries in the NUD_STALE state will be kept in the neighbour table as long as
the number of cache entries does not exceed the value specified in gc_thresh1.
This commit validates the state of a neighbour cache entry before using
the entry.
Signed-off-by: JianJhen Chen <kchen@synology.com>
Reviewed-by: JinLin Chen <jlchen@synology.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/bridge/br_stp_if.c')
0 files changed, 0 insertions, 0 deletions