diff options
author | Paul Moore <pmoore@redhat.com> | 2013-12-04 22:10:45 +0100 |
---|---|---|
committer | Paul Moore <pmoore@redhat.com> | 2013-12-12 23:21:31 +0100 |
commit | 47180068276a04ed31d24fe04c673138208b07a9 (patch) | |
tree | 957e58757aa1373a9e8696761f00f26d6b6704f8 /security/min_addr.c | |
parent | selinux: fix possible memory leak (diff) | |
download | linux-47180068276a04ed31d24fe04c673138208b07a9.tar.xz linux-47180068276a04ed31d24fe04c673138208b07a9.zip |
selinux: handle TCP SYN-ACK packets correctly in selinux_ip_output()
In selinux_ip_output() we always label packets based on the parent
socket. While this approach works in almost all cases, it doesn't
work in the case of TCP SYN-ACK packets when the correct label is not
the label of the parent socket, but rather the label of the larval
socket represented by the request_sock struct.
Unfortunately, since the request_sock isn't queued on the parent
socket until *after* the SYN-ACK packet is sent, we can't lookup the
request_sock to determine the correct label for the packet; at this
point in time the best we can do is simply pass/NF_ACCEPT the packet.
It must be said that simply passing the packet without any explicit
labeling action, while far from ideal, is not terrible as the SYN-ACK
packet will inherit any IP option based labeling from the initial
connection request so the label *should* be correct and all our
access controls remain in place so we shouldn't have to worry about
information leaks.
Reported-by: Janak Desai <Janak.Desai@gtri.gatech.edu>
Tested-by: Janak Desai <Janak.Desai@gtri.gatech.edu>
Cc: stable@vger.kernel.org
Signed-off-by: Paul Moore <pmoore@redhat.com>
Diffstat (limited to 'security/min_addr.c')
0 files changed, 0 insertions, 0 deletions