summaryrefslogtreecommitdiffstats
path: root/net/rxrpc
diff options
context:
space:
mode:
authorPaul Moore <pmoore@redhat.com>2013-03-25 03:18:33 +0000
committerDavid S. Miller <davem@davemloft.net>2013-03-25 13:11:48 -0400
commitded34e0fe8fe8c2d595bfa30626654e4b87621e0 (patch)
treec32940377c5650dfd93245964e5fdfcfd93ab528 /net/rxrpc
parent7ebe183c6d444ef5587d803b64a1f4734b18c564 (diff)
downloadop-kernel-dev-ded34e0fe8fe8c2d595bfa30626654e4b87621e0.zip
op-kernel-dev-ded34e0fe8fe8c2d595bfa30626654e4b87621e0.tar.gz
unix: fix a race condition in unix_release()
As reported by Jan, and others over the past few years, there is a race condition caused by unix_release setting the sock->sk pointer to NULL before properly marking the socket as dead/orphaned. This can cause a problem with the LSM hook security_unix_may_send() if there is another socket attempting to write to this partially released socket in between when sock->sk is set to NULL and it is marked as dead/orphaned. This patch fixes this by only setting sock->sk to NULL after the socket has been marked as dead; I also take the opportunity to make unix_release_sock() a void function as it only ever returned 0/success. Dave, I think this one should go on the -stable pile. Special thanks to Jan for coming up with a reproducer for this problem. Reported-by: Jan Stancek <jan.stancek@gmail.com> Signed-off-by: Paul Moore <pmoore@redhat.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/rxrpc')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud