First published: Wed Nov 15 2017(Updated: )
It was found that in Linux kernel 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. References: <a href="https://patchwork.ozlabs.org/patch/827077/">https://patchwork.ozlabs.org/patch/827077/</a> <a href="http://seclists.org/oss-sec/2017/q4/282">http://seclists.org/oss-sec/2017/q4/282</a> An upstream patch: <a href="https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=df80cd9b28b9ebaa284a41df611dbf3a2d05ca74">https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=df80cd9b28b9ebaa284a41df611dbf3a2d05ca74</a>
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel | <3.2.96 | |
Linux Kernel | >=3.3<3.16.51 | |
Linux Kernel | >=3.17<3.18.84 | |
Linux Kernel | >=3.19<4.1.47 | |
Linux Kernel | >=4.2<4.4.100 | |
Linux Kernel | >=4.5<4.9.65 | |
Linux Kernel | >=4.10<4.13.16 | |
Debian Linux | =7.0 | |
SUSE Linux Enterprise Server | =11-sp4 | |
Ubuntu | =12.04 | |
Ubuntu | =14.04 | |
Ubuntu | =16.04 | |
Ubuntu | =17.10 | |
debian/linux | 5.10.223-1 5.10.234-1 6.1.129-1 6.1.133-1 6.12.21-1 6.12.22-1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-15115 has a medium severity level due to the potential for unintended data exposure related to socket associations.
To mitigate CVE-2017-15115, you should upgrade your Linux kernel to version 5.10.223-1 or later, or apply the relevant patches provided by your distribution.
CVE-2017-15115 affects multiple versions of the Linux kernel, specifically versions prior to 5.10.223-1 and various earlier versions between 3.x and 4.x.
CVE-2017-15115 is not considered remotely exploitable as it requires local access to the system, affecting only users with elevated privileges.
CVE-2017-15115 may lead to inconsistent socket behavior and could potentially allow for unauthorized data retention in some network namespaces.