The following flaw was reported in the kernel: skb_copy_and_csum_datagram_iovec doesn't check the actual length of the iovec's buffers to which it copies data, then memcpy_toiovec can copy to an address that was not specified by userspace, but garbage lying on the kernel stack. In some cases, this address can be a valid userspace address, to which memcpy_toiovec will write the buffers. This can happen when userspace calls write followed by recvmsg. In that case, memcpy_toiovec will dump the packet contents to the buffer passed to the write call, and can for example overwrite stack contents. Upstream patch: http://patchwork.ozlabs.org/patch/530642/ CVE request and assignment: http://seclists.org/oss-sec/2015/q4/177
Created kernel tracking bugs for this issue: Affects: fedora-all [bug 1276589]
I don't think this is applicable to Fedora. The original report was here: http://www.openwall.com/lists/oss-security/2015/10/27/11 and that pointed out that impacted versions are only before 3.19 with a particular commit applied (89c22d8c3b27 ("net: Fix skb csum races when peeking")) but are lacking the ioviter conversion. The patch referenced in the initial comment also clearly spells this out. All Fedora releases are on 4.1.y or newer, and should not be affected by this.
Statement: This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2, as the code introduced the flaw is not present in these products.