Received: by 2002:a05:6a10:a852:0:0:0:0 with SMTP id d18csp494383pxy; Wed, 5 May 2021 07:12:30 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzAs0EPfX5ivoPzNTPo8QxTyCCUd+i8lW/Fq+HjZxtfu7iqB8tGZQGgdrlhrkr4vnnEkXkR X-Received: by 2002:a05:6402:1914:: with SMTP id e20mr32195014edz.70.1620223950047; Wed, 05 May 2021 07:12:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1620223950; cv=none; d=google.com; s=arc-20160816; b=xE8x5uOVcM+rD0IhcRkIZS8nBI0bbgGURXJgtrRTmOSA+zemYx92C1qVCv0RP2MyxD 39Orax1qdM+ArtCW/hcurBxdSnvkB4OSUeBqJDLoKGHZ6lqtJfC9OSTy68fP4loUv/hV GVDhzjyDeYM2Z5ZYTsRkk9i9Anq4lclcZHCx6wshK0G+gouBxIPMwbsufPGZiUpB0LYV Zo3sokIeNfch7gT8YtlRAT2/EEabKtd/cuAE73Egrok81wU5ScgU5Qzd+pK/Oz9ihoQp /zmX/is90IwyMaiFXXGA+/7DFdP7yHYxk2hj0HGwmp75MG/xrudPggDDONmliBNIWyqW tlng== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=wqFhUh4vsJzgbuT/cSfkveWn8nJZLuj0YsXled/4xps=; b=TgC7QM5uTsH8nsUuEime/1VqNPanVkSvw1P1R0Bn9kvPDkaQ2WsBqdpjxLc+rKLwMl npRyz9NsQnpHOT08MdnhQ2MPeSj84FK5I14Fz4NPjQwRQMoqDbZPiWSgbPT04VZKiNm1 O8swAYhBywzmH1Rs79lQKTQ1GFBXHCCHT+2cfjDjsAGjDDG18z3aQiVYYVM7+u84hpXF /VEBeo7rlnC8fNZcIi8Z+u3r/4cJs6Huaq9h6DGg+/47HODypdMHbYvJrFeZbcXRCNaS Mj3lyIoNBOxFc9zZJij8Nz17xuVZJt47DSOHfDiKIoT7HkVMhqslyPvQxnk2/5eegO/n QdrA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=zseHCLYp; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id y18si5671270ejj.34.2021.05.05.07.11.51; Wed, 05 May 2021 07:12:30 -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; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=zseHCLYp; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232400AbhEEMNc (ORCPT + 99 others); Wed, 5 May 2021 08:13:32 -0400 Received: from mail.kernel.org ([198.145.29.99]:50558 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233763AbhEEMJ3 (ORCPT ); Wed, 5 May 2021 08:09:29 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id A1240613FB; Wed, 5 May 2021 12:08:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1620216493; bh=w+ksNPRAa0KVoiUtvaDFov4RY9DMF4suTFHZxsLavNA=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=zseHCLYpl3vfN73Ve7mHMq7HVEAE5JgK083pzPEiX/JjShSmM38mfQdFkueRbJmPH lmUVNHo+LE2aNhnOGPjimRxsBFuE6HVDb4qKL4jtfIyjiFQWtLgs1xjSz3xNLN1U/9 dX8taAwD3Wyp/pcPJ6yzj1a+TND8T6bYzdGmB74k= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Daniel Borkmann , Piotr Krysiuk , John Fastabend , Alexei Starovoitov Subject: [PATCH 5.12 05/17] bpf: Fix masking negation logic upon negative dst register Date: Wed, 5 May 2021 14:06:00 +0200 Message-Id: <20210505112325.126024016@linuxfoundation.org> X-Mailer: git-send-email 2.31.1 In-Reply-To: <20210505112324.956720416@linuxfoundation.org> References: <20210505112324.956720416@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Daniel Borkmann commit b9b34ddbe2076ade359cd5ce7537d5ed019e9807 upstream. The negation logic for the case where the off_reg is sitting in the dst register is not correct given then we cannot just invert the add to a sub or vice versa. As a fix, perform the final bitwise and-op unconditionally into AX from the off_reg, then move the pointer from the src to dst and finally use AX as the source for the original pointer arithmetic operation such that the inversion yields a correct result. The single non-AX mov in between is possible given constant blinding is retaining it as it's not an immediate based operation. Fixes: 979d63d50c0c ("bpf: prevent out of bounds speculation on pointer arithmetic") Signed-off-by: Daniel Borkmann Tested-by: Piotr Krysiuk Reviewed-by: Piotr Krysiuk Reviewed-by: John Fastabend Acked-by: Alexei Starovoitov Signed-off-by: Greg Kroah-Hartman --- kernel/bpf/verifier.c | 12 ++++-------- 1 file changed, 4 insertions(+), 8 deletions(-) --- a/kernel/bpf/verifier.c +++ b/kernel/bpf/verifier.c @@ -11760,14 +11760,10 @@ static int fixup_bpf_calls(struct bpf_ve *patch++ = BPF_ALU64_REG(BPF_OR, BPF_REG_AX, off_reg); *patch++ = BPF_ALU64_IMM(BPF_NEG, BPF_REG_AX, 0); *patch++ = BPF_ALU64_IMM(BPF_ARSH, BPF_REG_AX, 63); - if (issrc) { - *patch++ = BPF_ALU64_REG(BPF_AND, BPF_REG_AX, - off_reg); - insn->src_reg = BPF_REG_AX; - } else { - *patch++ = BPF_ALU64_REG(BPF_AND, off_reg, - BPF_REG_AX); - } + *patch++ = BPF_ALU64_REG(BPF_AND, BPF_REG_AX, off_reg); + if (!issrc) + *patch++ = BPF_MOV64_REG(insn->dst_reg, insn->src_reg); + insn->src_reg = BPF_REG_AX; if (isneg) insn->code = insn->code == code_add ? code_sub : code_add;