diff options
author | Christoph Paasch <cpaasch@apple.com> | 2017-12-11 00:05:46 -0800 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2017-12-12 11:15:42 -0500 |
commit | 30791ac41927ebd3e75486f9504b6d2280463bf0 (patch) | |
tree | 7d1bc27f38566a3ac0e7bd7a32fa6b998a9440a2 /kernel | |
parent | 200809716aed1cac586fcac4c0551a688439be1f (diff) | |
download | linux-stable-30791ac41927ebd3e75486f9504b6d2280463bf0.tar.gz linux-stable-30791ac41927ebd3e75486f9504b6d2280463bf0.tar.bz2 linux-stable-30791ac41927ebd3e75486f9504b6d2280463bf0.zip |
tcp md5sig: Use skb's saddr when replying to an incoming segment
The MD5-key that belongs to a connection is identified by the peer's
IP-address. When we are in tcp_v4(6)_reqsk_send_ack(), we are replying
to an incoming segment from tcp_check_req() that failed the seq-number
checks.
Thus, to find the correct key, we need to use the skb's saddr and not
the daddr.
This bug seems to have been there since quite a while, but probably got
unnoticed because the consequences are not catastrophic. We will call
tcp_v4_reqsk_send_ack only to send a challenge-ACK back to the peer,
thus the connection doesn't really fail.
Fixes: 9501f9722922 ("tcp md5sig: Let the caller pass appropriate key for tcp_v{4,6}_do_calc_md5_hash().")
Signed-off-by: Christoph Paasch <cpaasch@apple.com>
Reviewed-by: Eric Dumazet <edumazet@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions