Received: by 2002:a05:6a11:4021:0:0:0:0 with SMTP id ky33csp2353046pxb; Mon, 20 Sep 2021 19:50:50 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz5YVjR1Qi0uV1Nhp1youpJBSEsIdoGLSigdBqMcqgS8vdz+fVDVR0mnhVbXZzO9WkI5rhp X-Received: by 2002:a02:998a:: with SMTP id a10mr20596800jal.23.1632192650093; Mon, 20 Sep 2021 19:50:50 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1632192650; cv=none; d=google.com; s=arc-20160816; b=vDptTg02Tr2cG10hQlyXHJQVnt8ebsuaD4sTdz6BTvFHLHeBFMwhOOYNWCy3PqlLx8 4U4RQqNY8YakgFfeVJaNxuojBuRzs+cJcnBYb4PYDPNffTYZ1SCzvBcNBZH4202W8RA8 T0OkqkoYqbFvwcdzi0S+vzey1hQBTqhQwzdL0NMRsk9oB/fwOsxt9wrZcf589k9/Vrjm k1xs/ms2qaY2BXz7YcWmYZ+HBNGjqlJt+9eHHULyFabHVqQbSDrREO2S5ZVMXPabMd/+ i7zCoBQXBzZgNziG7jFX/sCzKVFd9HRl7Q8rGBHH8coTRHO6lxWLQcEtlsWZYXjZwFCP T/LA== 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=XpHvNzPmVh6zrA0PBaNnbPrNdLb6bxaq5NTWrEXUO0A=; b=uxOmLasXkMAdatm+ERVtoSsirhqz37GLM8h2X/UGA2jFqbjqjHNDNog1fWAL1iOsrh Ff+p6e0HJv+pb4Cn02SicLj3keUzGjmbcYthx1llVmgjD9QKGxTPhFdXvC+m5QbyHDta +b+BBGXfnaUx2g1PeDgyyjyduvs6OiexiOu2Dxmer5pVpiLMezaWhMWmO1rLq9mVEs4D lBE+T65EB+cxOJcFfhEwfgoQcdgfG4au5jZFVKGtBTx8k8W/dzTin4YWAKObMoYupB5J 5laVXCdzMIe6WJ6YeEckEKHMmpgl9DKa3PeDaRQ+OAGjsBxPajOTKVXQzHMPCpaZizPV /z0w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=ZqexsyE0; 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 y12si1676760ilv.168.2021.09.20.19.50.39; Mon, 20 Sep 2021 19:50:50 -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=ZqexsyE0; 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 S1346955AbhITSnG (ORCPT + 99 others); Mon, 20 Sep 2021 14:43:06 -0400 Received: from mail.kernel.org ([198.145.29.99]:53066 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1381484AbhITSiW (ORCPT ); Mon, 20 Sep 2021 14:38:22 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 14AD26331D; Mon, 20 Sep 2021 17:29:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1632158998; bh=YUVk19KBBd5oNKIWdem0ilUR52CnlfnPNYdNYsXsA3Y=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=ZqexsyE01t5IOVNHUKxl2V4KQmpQosetVEBDxO0NW1Ln+TMP84XFON4sONFEajPAx 40KDuBlFHIBg1IDZZG7Ft/j0nv0gKRdR6xubPTq7luBFWv+twS6wHxVMI4veeZwugK 4rJPfWhXMfAv7BbY3M5V2ZQTrnI8v2KQpG97fJEI= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Mark Brown , Catalin Marinas Subject: [PATCH 5.14 007/168] arm64/sve: Use correct size when reinitialising SVE state Date: Mon, 20 Sep 2021 18:42:25 +0200 Message-Id: <20210920163921.888344722@linuxfoundation.org> X-Mailer: git-send-email 2.33.0 In-Reply-To: <20210920163921.633181900@linuxfoundation.org> References: <20210920163921.633181900@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: Mark Brown commit e35ac9d0b56e9efefaeeb84b635ea26c2839ea86 upstream. When we need a buffer for SVE register state we call sve_alloc() to make sure that one is there. In order to avoid repeated allocations and frees we keep the buffer around unless we change vector length and just memset() it to ensure a clean register state. The function that deals with this takes the task to operate on as an argument, however in the case where we do a memset() we initialise using the SVE state size for the current task rather than the task passed as an argument. This is only an issue in the case where we are setting the register state for a task via ptrace and the task being configured has a different vector length to the task tracing it. In the case where the buffer is larger in the traced process we will leak old state from the traced process to itself, in the case where the buffer is smaller in the traced process we will overflow the buffer and corrupt memory. Fixes: bc0ee4760364 ("arm64/sve: Core task context handling") Cc: # 4.15.x Signed-off-by: Mark Brown Link: https://lore.kernel.org/r/20210909165356.10675-1-broonie@kernel.org Signed-off-by: Catalin Marinas Signed-off-by: Greg Kroah-Hartman --- arch/arm64/kernel/fpsimd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/arch/arm64/kernel/fpsimd.c +++ b/arch/arm64/kernel/fpsimd.c @@ -511,7 +511,7 @@ size_t sve_state_size(struct task_struct void sve_alloc(struct task_struct *task) { if (task->thread.sve_state) { - memset(task->thread.sve_state, 0, sve_state_size(current)); + memset(task->thread.sve_state, 0, sve_state_size(task)); return; }