diff options
author | Leonard Crestez <cdleonard@gmail.com> | 2021-10-15 10:26:04 +0300 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2021-10-15 16:36:57 +0300 |
commit | 86f1e3a8489f6a0232c1f3bc2bdb379f5ccdecec (patch) | |
tree | c8c840d9f264202e0a3314689fbb67ac48d1cfd2 /include/net/tcp.h | |
parent | 46393d61a328d7c4e3264252dae891921126c674 (diff) | |
download | linux-86f1e3a8489f6a0232c1f3bc2bdb379f5ccdecec.tar.xz |
tcp: md5: Fix overlap between vrf and non-vrf keys
With net.ipv4.tcp_l3mdev_accept=1 it is possible for a listen socket to
accept connection from the same client address in different VRFs. It is
also possible to set different MD5 keys for these clients which differ
only in the tcpm_l3index field.
This appears to work when distinguishing between different VRFs but not
between non-VRF and VRF connections. In particular:
* tcp_md5_do_lookup_exact will match a non-vrf key against a vrf key.
This means that adding a key with l3index != 0 after a key with l3index
== 0 will cause the earlier key to be deleted. Both keys can be present
if the non-vrf key is added later.
* _tcp_md5_do_lookup can match a non-vrf key before a vrf key. This
casues failures if the passwords differ.
Fix this by making tcp_md5_do_lookup_exact perform an actual exact
comparison on l3index and by making __tcp_md5_do_lookup perfer
vrf-bound keys above other considerations like prefixlen.
Fixes: dea53bb80e07 ("tcp: Add l3index to tcp_md5sig_key and md5 functions")
Signed-off-by: Leonard Crestez <cdleonard@gmail.com>
Reviewed-by: David Ahern <dsahern@kernel.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'include/net/tcp.h')
0 files changed, 0 insertions, 0 deletions