Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp2334798ybz; Thu, 23 Apr 2020 16:14:08 -0700 (PDT) X-Google-Smtp-Source: APiQypK/krgeCbrx/tU7553voxoc3zvt5QzboXQtARM0eOB7/zS6pu5UKrnbcur1Uqw+Q0UKOgUz X-Received: by 2002:a50:eb8b:: with SMTP id y11mr4920260edr.229.1587683647817; Thu, 23 Apr 2020 16:14:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1587683647; cv=none; d=google.com; s=arc-20160816; b=mrti2HIQle7sEaOtjkgmI1gTEJcm3BQSAGHor91nOJ0OCqkVOm8MBWrWQ2Zv8MQJhQ VrPz91nZnbzVKhSUaQVFnDLlO/OLRVxtfxVsQEDeVrhVZ02evj1Nig755kYoinjnW7Ez OZxoBvhE9C/+uNXfq33gkwGNUYpigC9vKdhNKBbdqEbn6MqOjM0o4S4TnnU5Hj7Bv8J+ ZNrtitX9zqvwBQyTU2qLyznnW6LtxPvWBdeSlxF8mMQQXqdrRhRY5AoKl8i1Zb2LWX5S yB0ibWX3InZHZCox4f0NOW4Q44xpflp6dA09GX0WFE0IHdSjauWnvoLN/mygzlqdwuAH sghg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:subject:message-id:date:cc:to :from:mime-version:content-transfer-encoding:content-disposition; bh=7iyUHeZe1Snh/F7Qy6GF9vJfHyCZ9hVQNB+hMk3b53w=; b=o0inEd4RxjJ51Pw8iL8NKdFz5wRF1RFVar5N3lUmWCeYuKFYjffxs20td5HiBuUsWL L/aWA+izunqscEB23NVGZfBaLdlAU41k99rJVpSzrhoL0Q0hrXsxt+PqDdr5orgYjQ3A v3aTYXE8Gnx5IpEq4GrWN8sYmsd+iWBDs89ju8lEFgRg3SW9yW6L3xYOsAzyNJscHILM HejtZu1lmgWiPxI4velEPfD+jF2p9o8ArZuZGm+6lJeagFWDRYNkv+pUQjzceNp0hkmj 5Q1rr3YI4xzKFiRsrojuT9l/0j6U7IxwLhq/nmnGRmU1ufCwG9QLHa3cIqwgsMuVHN9r elFA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id d6si1877325edy.66.2020.04.23.16.13.44; Thu, 23 Apr 2020 16:14:07 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729194AbgDWXK5 (ORCPT + 99 others); Thu, 23 Apr 2020 19:10:57 -0400 Received: from shadbolt.e.decadent.org.uk ([88.96.1.126]:50306 "EHLO shadbolt.e.decadent.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728589AbgDWXGw (ORCPT ); Thu, 23 Apr 2020 19:06:52 -0400 Received: from [192.168.4.242] (helo=deadeye) by shadbolt.decadent.org.uk with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1jRkve-0004mS-7f; Fri, 24 Apr 2020 00:06:46 +0100 Received: from ben by deadeye with local (Exim 4.93) (envelope-from ) id 1jRkvZ-00E6z2-1M; Fri, 24 Apr 2020 00:06:41 +0100 Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 From: Ben Hutchings To: linux-kernel@vger.kernel.org, stable@vger.kernel.org CC: akpm@linux-foundation.org, Denis Kirjanov , "Eric Dumazet" , "David S. Miller" , "Eric Dumazet" , syzbot+2f07903a5b05e7f36410@syzkaller.appspotmail.com, "Cong Wang" Date: Fri, 24 Apr 2020 00:07:14 +0100 Message-ID: X-Mailer: LinuxStableQueue (scripts by bwh) X-Patchwork-Hint: ignore Subject: [PATCH 3.16 207/245] net_sched: fix datalen for ematch In-Reply-To: X-SA-Exim-Connect-IP: 192.168.4.242 X-SA-Exim-Mail-From: ben@decadent.org.uk X-SA-Exim-Scanned: No (on shadbolt.decadent.org.uk); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 3.16.83-rc1 review patch. If anyone has any objections, please let me know. ------------------ From: Cong Wang commit 61678d28d4a45ef376f5d02a839cc37509ae9281 upstream. syzbot reported an out-of-bound access in em_nbyte. As initially analyzed by Eric, this is because em_nbyte sets its own em->datalen in em_nbyte_change() other than the one specified by user, but this value gets overwritten later by its caller tcf_em_validate(). We should leave em->datalen untouched to respect their choices. I audit all the in-tree ematch users, all of those implement ->change() set em->datalen, so we can just avoid setting it twice in this case. Reported-and-tested-by: syzbot+5af9a90dad568aa9f611@syzkaller.appspotmail.com Reported-by: syzbot+2f07903a5b05e7f36410@syzkaller.appspotmail.com Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2") Cc: Eric Dumazet Signed-off-by: Cong Wang Reviewed-by: Eric Dumazet Signed-off-by: David S. Miller [bwh: Backported to 3.16: adjust context] Signed-off-by: Ben Hutchings --- net/sched/ematch.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/net/sched/ematch.c +++ b/net/sched/ematch.c @@ -266,12 +266,12 @@ static int tcf_em_validate(struct tcf_pr } em->data = (unsigned long) v; } + em->datalen = data_len; } } em->matchid = em_hdr->matchid; em->flags = em_hdr->flags; - em->datalen = data_len; err = 0; errout: