@SolSoCoG is it listed in /proc/net/udp? Also, could be the owning process hasn't be reaped by its parent so it is in a zombie state and therefore holding onto socket.