From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751231AbdEPFxx (ORCPT ); Tue, 16 May 2017 01:53:53 -0400 Received: from mail-yb0-f178.google.com ([209.85.213.178]:35857 "EHLO mail-yb0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750765AbdEPFxv (ORCPT ); Tue, 16 May 2017 01:53:51 -0400 MIME-Version: 1.0 In-Reply-To: <20170516052009.GA17400@1wt.eu> References: <20170516052009.GA17400@1wt.eu> From: Steven Pease Date: Mon, 15 May 2017 22:53:50 -0700 Message-ID: Subject: Re: CVE-2016-10229 in 4.4.x series To: Willy Tarreau Cc: linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Is there any particular reason that the CVE appears to be filed against 4.4.60? Or is this just a mistake? http://www.cvedetails.com/cve/CVE-2016-10229/ - Steven On Mon, May 15, 2017 at 10:20 PM, Willy Tarreau wrote: > On Mon, May 15, 2017 at 06:09:53PM -0700, Steven Pease wrote: >> Hi, >> >> This is my first post - not currently subscribed so please CC me. :) I >> searched a bit for this question, but couldn't find an answer (Googled >> '2016-10229 site:lkml.org'). >> >> Does CVE-2016-10229 affect the newest version of the 4.4.x kernel >> series (currently 4.4.68) and are there any plans to fix this in the >> 4.4 kernel series? > > This one was fixed by upstream commit 197c949 ("udp: properly support > MSG_PEEK with truncated buffers"), which was backported in 4.4 as > commit dfe2042d96 in 4.4.21. So in short, 4.4.68 is safe. > > Willy -- - Steven