CVE-2017-15115: Use After Free
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:
https://patchwork.ozlabs.org/patch/827077/
http://seclists.org/oss-sec/2017/q4/282
An upstream patch:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=df80cd9b28b9ebaa284a41df611dbf3a2d05ca74
Other sources
The sctpdopeeloff function in net/sctp/socket.c in the Linux kernel before 4.14 does not check whether the intended netns is used in a peel-off action, which allows local users to cause a denial of service (use-after-free and system crash) or possibly have unspecified other impact via crafted system calls.
— Launchpad
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 5.10.223-1Fixed in 5.10.262-1Fixed in 6.1.176-1Fixed in 6.1.180-1Fixed in 6.12.94-1Fixed in 6.12.101-1Fixed in 7.1.8-1Fixed in 7.1.8-2 - Upgrade
Upgrade
Linux kernelto a version that resolves this vulnerability.Patch df80cd9b28b9ebaa284a41df611dbf3a2d05ca74 - Upgrade
Upgrade
Linux kernelto a version that resolves this vulnerability.Patch 827077
Event History
Frequently Asked Questions
What is the severity of CVE-2017-15115?
CVE-2017-15115 has a medium severity level due to the potential for unintended data exposure related to socket associations.
How do I fix CVE-2017-15115?
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.
Which versions of Linux are affected by CVE-2017-15115?
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.
Is CVE-2017-15115 exploitable remotely?
CVE-2017-15115 is not considered remotely exploitable as it requires local access to the system, affecting only users with elevated privileges.
What types of network issues could CVE-2017-15115 cause?
CVE-2017-15115 may lead to inconsistent socket behavior and could potentially allow for unauthorized data retention in some network namespaces.