It was found that in Linux kernel before 4.14 when peeling off an association to the socket in another network namespace, all transports in this association are not to be rehashed and keep use the old key in hashtable. A kernel would miss removing transports from hashtable when closing the socket and all transports are being freed. Later on a use-after-free issue could be caused when looking up an association and dereferencing the transports.
It was found that in Linux kernel before 4.14 when peeling off an association to the socket in another network namespace, all transports in this association are not to be rehashed and keep use the old key in hashtable. A kernel would miss removing transports from hashtable when closing the socket and all transports are being freed. Later on a use-after-free issue could be caused when looking up an association and dereferencing the transports.
https://git.kernel.org/linus/df80cd9b28b9ebaa284a41df611dbf3a2d05ca74 https://bugzilla.redhat.com/show_bug.cgi?id=1513345 http://seclists.org/oss-sec/2017/q4/282
Vulmon