7.8
CVSSv3

CVE-2017-15115

Published: 15/11/2017 Updated: 19/01/2023
CVSS v2 Base Score: 7.2 | Impact Score: 10 | Exploitability Score: 3.9
CVSS v3 Base Score: 7.8 | Impact Score: 5.9 | Exploitability Score: 1.8
VMScore: 642
Vector: AV:L/AC:L/Au:N/C:C/I:C/A:C

Vulnerability Summary

The sctp_do_peeloff function in net/sctp/socket.c in the Linux kernel prior to 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.

Vulnerability Trend

Vulnerable Product Search on Vulmon Subscribe to Product

linux linux kernel

debian debian linux 7.0

suse linux enterprise server 11

canonical ubuntu linux 16.04

canonical ubuntu linux 14.04

canonical ubuntu linux 12.04

canonical ubuntu linux 17.10

Vendor Advisories

A flaw was found in the patches used to fix the 'dirtycow' vulnerability (CVE-2016-5195) An attacker, able to run local code, can exploit a race condition in transparent huge pages to modify usually read-only huge pages (CVE-2017-1000405) Linux kernel Virtualization Module (CONFIG_KVM) for the Intel processor family (CONFIG_KVM_INTEL) is vulnerab ...
A vulnerability was found in the 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 using the old key in hashtable, thus removing transports from hashtable when closing the socket, all transports are being freed Later on a use-after-free issue ...
Several security issues were fixed in the Linux kernel ...
Several security issues were fixed in the Linux kernel ...
Several security issues were fixed in the Linux kernel ...
Several security issues were fixed in the Linux kernel ...
Several security issues were fixed in the Linux kernel ...
Several security issues were fixed in the Linux kernel ...
It was found that in Linux kernel before 414 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-a ...