Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp4626008pxb; Tue, 25 Jan 2022 14:52:44 -0800 (PST) X-Google-Smtp-Source: ABdhPJxokEWWM5IHjXGivGgoca+BDhF+qU+g9JyFamPsg23RaBtc3f8j9BfdzQ2s28xzRyDR4McS X-Received: by 2002:a63:7546:: with SMTP id f6mr16650351pgn.480.1643151164505; Tue, 25 Jan 2022 14:52:44 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643151164; cv=none; d=google.com; s=arc-20160816; b=MDCQQM79txEqcdPBD7G171aKGId1dKKL+ooWivRTq9XCOweGfqvZJZM/rQfKOEuqxU benB1TT+ValT28M15b5dbN359fUwHVsxVCW/NpFXEwt1EjgQ1K+A9gPBfVrp+M0ddhW0 yCq7t/qsdPbUssgBvq52cYZXEY4KjA3jsz5m0ZzmAx5Fje4tlm5YANLBE3KyXKL6Sb5m K1M0psyQisOp8/jbsOL9EaHZ3+Cgco2pKhgpHf89oAtDshUJO52UeOWuSqlk9VYcm3cw nWtYlpsD6Uf+sML9Xh3b0md5frdMk3O4K2vCgEMT0BGU75vDEupsNu/kdODN0a98VP/y 3RMQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=R+cU466+BZbGpeQFzEB83w6Thya/8ZdOJGMCPR/hDRw=; b=hHQcejDTfAJa6Y+slK1cAEuHWquWg2+pA4fhy0p0HurieUF6LRcGyaQ6DZV6VKPZYY YR9RwHeQJUAO71C7iD2HXUI4xit5mSlq9gQ+4EykAyBuX36bsG5GsDFbdRbsFNjvI+dz Cczsh+rcLw9HUHAiKMYj9YAmtjQH8Iwpyr2TX4DngVACCE02QruLpIEmNXakGz+RO72G vxfqtZiwO1dh7ijM/l4SUnZddcYLF2jzurb+lKngW5cuNDJGh21lOpVpM3oMxz4QquGx xh9sat1tXGWJTDvNmL0gTPl9vs/0AhCpM7XogPSji2IDR5dOtstSdxD2F6b2s8/xHm6s KOsw== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id l17si9668131pls.155.2022.01.25.14.52.32; Tue, 25 Jan 2022 14:52:44 -0800 (PST) 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1582645AbiAYPwh (ORCPT + 99 others); Tue, 25 Jan 2022 10:52:37 -0500 Received: from foss.arm.com ([217.140.110.172]:51900 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1582582AbiAYPuM (ORCPT ); Tue, 25 Jan 2022 10:50:12 -0500 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 2F1C9D6E; Tue, 25 Jan 2022 07:50:08 -0800 (PST) Received: from FVFF77S0Q05N (unknown [10.57.1.45]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id BCC023F793; Tue, 25 Jan 2022 07:50:06 -0800 (PST) Date: Tue, 25 Jan 2022 15:50:01 +0000 From: Mark Rutland To: Evgenii Stepanov Cc: Catalin Marinas , Will Deacon , Ard Biesheuvel , Robin Murphy , Jisheng Zhang , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] arm64: extable: fix null deref in load_unaligned_zeropad. Message-ID: References: <20220122023447.1480995-1-eugenis@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 25, 2022 at 03:23:20PM +0000, Mark Rutland wrote: > On Fri, Jan 21, 2022 at 06:34:47PM -0800, Evgenii Stepanov wrote: > > ex_handler_load_unaligned_zeropad extracts the source and data register > > numbers from the wrong field of the exception table. > > Ouch. Did you find this by inspection, or did this show up in testing? > > Sorry about this. > > I think we should be a little more explicit as to exactly what goes wrong. How > about: > > | In ex_handler_load_unaligned_zeropad() we erroneously extract the data and > | addr register indices from ex->type rather than ex->data. As ex->type will > | contain EX_TYPE_LOAD_UNALIGNED_ZEROPAD (i.e. 4): > | > | * We'll always treat X0 as the address register, since EX_DATA_REG_ADDR is > | extracted from bits [9:5]. Thus, we may attempt to dereference an arbitrary > | address as X0 may hold an arbitary value. > | > | * We'll always treat X4 as the data register, since EX_DATA_REG_DATA is > | extracted from bits [4:0]. Thus we will corrupt X4 and cause arbitrary > | behaviour within load_unaligned_zeropad() and its caller. > | > | Fix this by extracting both values from ex->data as originally intended. > > > Fixes: 753b3236 > > That should be expanded, e.g. > > Fixes: 753b32368705c396 ("arm64: extable: add load_unaligned_zeropad() handler") > > With those changes: > > Reviewed-by: Mark Rutland Looking again, sicne this isn't jsut a null-deref, can we also rework the title, something like: | arm64: extable: fix load_unaligned_zeropad() reg indices Thanks, Mark.