CVE-2017-18509: Input Validation
An issue was discovered in net/ipv6/ip6mr.c in the Linux kernel before 4.11. By setting a specific socket option, an attacker can control a pointer in kernel land and cause an inetcsklistenstop general protection fault, or potentially execute arbitrary code under certain circumstances. The issue can be triggered as root (e.g., inside a default LXC container or with the CAPNETADMIN capability) or after namespace unsharing. This occurs because sktype and protocol are not checked in the appropriate part of the ip6mroute functions. NOTE: this affects Linux distributions that use 4.9.x longterm kernels before 4.9.187.
Other sources
In ip6mroutesetsockopt and related functions of ip6mr.c, there is a possible out of bounds write due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
— OSV
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
android/:linux_kernel:to a version that resolves this vulnerability.Fixed in :2021-02-05 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.115-2Fixed in 7.2.12-1Fixed in 7.2.15-1
Event History
Frequently Asked Questions
What is the vulnerability ID for this issue?
The vulnerability ID for this issue is CVE-2017-18509.
What is the severity level of CVE-2017-18509?
CVE-2017-18509 has a severity level of high.
Which software is affected by CVE-2017-18509?
CVE-2017-18509 affects various versions of the Linux kernel, including linux-gcp, linux-gcp-edge, linux-gke-4.15, linux, linux-aws, linux-aws-hwe, linux-azure, linux-azure-edge, linux-gke-5.0, linux-hwe, linux-hwe-edge, linux-kvm, linux-lts-trusty, linux-lts-xenial, linux-oem, linux-oracle, linux-raspi2, linux-snapdragon, and Google Android.
How can an attacker exploit CVE-2017-18509?
An attacker can exploit CVE-2017-18509 by setting a specific socket option, which allows them to control a pointer in the kernel and potentially execute arbitrary code.
Are there any patches or remedies available for CVE-2017-18509?
Yes, there are patches available to fix CVE-2017-18509. Please refer to the relevant sources for more information and updates.