A use after free vulnerability was found in the kernels socket recvmsg subsystem. This may allows remote attackers to corrupt memory and may allow execution of arbitrary code. This corruption takes place during the error handling routines within __sys_recvmmsg() function. To attack the kernel using this method the system must be running application using the UDP recvmmsg syscall(). Upstream patch: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=34b88a68f26a75e4fded796f1a49c40f82234b7d Upstream discussion: https://patchwork.kernel.org/patch/8093221/ Additional Write up: https://blog.lizzie.io/notes-about-cve-2016-7117.html
Created kernel tracking bugs for this issue: Affects: fedora-all [bug 1382269]
Statement: This issue affects the Linux kernels as shipped with Red Hat Enterprise Linux 5, 6, 7, MRG-2 and realtime and may be addressed in a future update.
This issue has been addressed in the following products: Red Hat Enterprise Linux 5 Via RHSA-2016:2962 https://rhn.redhat.com/errata/RHSA-2016-2962.html
This issue has been addressed in the following products: Red Hat Enterprise Linux 6.7 Extended Update Support Via RHSA-2017:0031 https://rhn.redhat.com/errata/RHSA-2017-0031.html
This issue has been addressed in the following products: Red Hat Enterprise Linux 6 Via RHSA-2017:0036 https://rhn.redhat.com/errata/RHSA-2017-0036.html
This issue has been addressed in the following products: Red Hat Enterprise Linux 6.5 Advanced Update Support Red Hat Enterprise Linux 6.5 Telco Extended Update Support Via RHSA-2017:0065 https://rhn.redhat.com/errata/RHSA-2017-0065.html
This issue has been addressed in the following products: Red Hat Enterprise MRG 2 Via RHSA-2017:0113 https://rhn.redhat.com/errata/RHSA-2017-0113.html
This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Via RHSA-2017:0086 https://rhn.redhat.com/errata/RHSA-2017-0086.html
This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Via RHSA-2017:0091 https://rhn.redhat.com/errata/RHSA-2017-0091.html
This issue has been addressed in the following products: Red Hat Enterprise Linux 6.4 Advanced Update Support Via RHSA-2017:0196 https://rhn.redhat.com/errata/RHSA-2017-0196.html
This issue has been addressed in the following products: Red Hat Enterprise Linux 6.2 Advanced Update Support Via RHSA-2017:0215 https://rhn.redhat.com/errata/RHSA-2017-0215.html
This issue has been addressed in the following products: Red Hat Enterprise Linux 7.2 Extended Update Support Via RHSA-2017:0217 https://rhn.redhat.com/errata/RHSA-2017-0217.html
This issue has been addressed in the following products: Red Hat Enterprise Linux 6.6 Advanced Update Support Red Hat Enterprise Linux 6.6 Telco Extended Update Support Via RHSA-2017:0216 https://rhn.redhat.com/errata/RHSA-2017-0216.html
This issue has been addressed in the following products: Red Hat Enterprise Linux 7.1 Extended Update Support Via RHSA-2017:0270 https://rhn.redhat.com/errata/RHSA-2017-0270.html
To exploit this issue, the attacker must be able to leverage a specific setup of the application/socket that is being targeted. In addition, specific timing behavior must be met for the affected code to be in a state where it can be exploited, making the exploitation of this flaw under normal conditions fairly difficult. In detail, the targeted socket on the remote end must be closed/terminated, which may trigger the error (use-after-free), which then allows for the exploitation to happen.
*** Bug 1489092 has been marked as a duplicate of this bug. ***