First published: Fri Feb 17 2017(Updated: )
A flaw was found in the linux kernels implementation of DCCP protocol in which a local user could create influence timing in which a skbuff could be used after it had been freed by the kernel. An attacker is able to craft structures allocated in this free memory will be able to create memory corruption, privilege escalation or crash the system. An attacker must have a local account access on the system, this is not a remote attack. An attack requires IPV6 support to be enabled in the system. Initial message: <a href="https://groups.google.com/forum/#!topic/syzkaller/_vGUxJLcdKY">https://groups.google.com/forum/#!topic/syzkaller/_vGUxJLcdKY</a> Proposed patch: <a href="https://patchwork.ozlabs.org/patch/728808/">https://patchwork.ozlabs.org/patch/728808/</a>
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/kernel | <0:2.6.18-419.el5 | 0:2.6.18-419.el5 |
redhat/kernel | <0:2.6.18-238.58.1.el5 | 0:2.6.18-238.58.1.el5 |
redhat/kernel | <0:2.6.18-348.33.1.el5 | 0:2.6.18-348.33.1.el5 |
redhat/kernel | <0:2.6.32-642.13.2.el6 | 0:2.6.32-642.13.2.el6 |
redhat/kernel | <0:2.6.32-220.70.1.el6 | 0:2.6.32-220.70.1.el6 |
redhat/kernel | <0:2.6.32-358.77.1.el6 | 0:2.6.32-358.77.1.el6 |
redhat/kernel | <0:2.6.32-431.78.1.el6 | 0:2.6.32-431.78.1.el6 |
redhat/kernel | <0:2.6.32-504.57.1.el6 | 0:2.6.32-504.57.1.el6 |
redhat/kernel | <0:2.6.32-573.40.1.el6 | 0:2.6.32-573.40.1.el6 |
redhat/kernel-rt | <0:3.10.0-514.6.1.rt56.430.el7 | 0:3.10.0-514.6.1.rt56.430.el7 |
redhat/kernel | <0:3.10.0-514.6.2.el7 | 0:3.10.0-514.6.2.el7 |
redhat/kernel | <0:3.10.0-229.49.1.ael7b | 0:3.10.0-229.49.1.ael7b |
redhat/kernel | <0:3.10.0-327.49.2.el7 | 0:3.10.0-327.49.2.el7 |
redhat/kernel-rt | <1:3.10.0-514.rt56.219.el6 | 1:3.10.0-514.rt56.219.el6 |
redhat/rhev-hypervisor7 | <0:7.3-20170425.0.el6e | 0:7.3-20170425.0.el6e |
redhat/rhev-hypervisor7 | <0:7.3-20170425.0.el7e | 0:7.3-20170425.0.el7e |
Linux Linux kernel | <3.2.86 | |
Linux Linux kernel | >=3.3<3.10.106 | |
Linux Linux kernel | >=3.11<3.12.71 | |
Linux Linux kernel | >=3.13<3.16.41 | |
Linux Linux kernel | >=3.17<3.18.49 | |
Linux Linux kernel | >=3.19<4.1.41 | |
Linux Linux kernel | >=4.2<4.4.52 | |
Linux Linux kernel | >=4.5<4.9.13 | |
Debian Debian Linux | =8.0 | |
Google Android | ||
debian/linux | 5.10.223-1 5.10.226-1 6.1.115-1 6.1.119-1 6.11.10-1 6.12.5-1 |
Recent versions of the SELinux policy can mitigate this flaw. The steps below will work with SELinux enabled or disabled. As the DCCP module will be auto-loaded when required, its use can be disabled by preventing the module from loading with the following instructions: # echo "install dccp /bin/true" >> /etc/modprobe.d/disable-dccp.conf The system will need to be restarted if the DCCP modules are loaded. In most circumstances, the DCCP kernel modules will be unable to be unloaded while any network interfaces are active and the protocol is in use. If you need further assistance, see KCS article https://access.redhat.com/solutions/41278 or contact Red Hat Global Support Services.
Blacklist the dccp ipv[46] autoloading aliases by adding the following lines to /etc/modprobe.d/blacklist-dccp.conf: alias net-pf-2-proto-0-type-6 off alias net-pf-2-proto-33-type-6 off alias net-pf-10-proto-0-type-6 off alias net-pf-10-proto-33-type-6 off
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
(Appears in the following advisories)