From patchwork Fri Mar 29 04:44:58 2024 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Deepak Gupta X-Patchwork-Id: 13610070 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4046CCD1283 for ; Fri, 29 Mar 2024 04:47:13 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 9EDC66B00C2; Fri, 29 Mar 2024 00:47:12 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 99D686B00C5; Fri, 29 Mar 2024 00:47:12 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 7A2E36B00C6; Fri, 29 Mar 2024 00:47:12 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0013.hostedemail.com [216.40.44.13]) by kanga.kvack.org (Postfix) with ESMTP id 5796C6B00C2 for ; Fri, 29 Mar 2024 00:47:11 -0400 (EDT) Received: from smtpin24.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay06.hostedemail.com (Postfix) with ESMTP id 29240A178A for ; Fri, 29 Mar 2024 04:47:11 +0000 (UTC) X-FDA: 81948842262.24.3679DAD Received: from mail-oo1-f54.google.com (mail-oo1-f54.google.com [209.85.161.54]) by imf08.hostedemail.com (Postfix) with ESMTP id 6A7D1160012 for ; Fri, 29 Mar 2024 04:47:09 +0000 (UTC) Authentication-Results: imf08.hostedemail.com; dkim=pass header.d=rivosinc-com.20230601.gappssmtp.com header.s=20230601 header.b=sUPMyesV; dmarc=none; spf=pass (imf08.hostedemail.com: domain of debug@rivosinc.com designates 209.85.161.54 as permitted sender) smtp.mailfrom=debug@rivosinc.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1711687629; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=9MOz30J7VxjH8ZagxzRr7bVMOq1rQVKKUTnSRMNh/j0=; b=br1xSHf+4vBp2B/xFiB4PKr9W1h0esNiiusmN0MqkRqUY/U9GC+D3xI/U5XudtEE3MZLi/ FKn51YXYnZWIFQeyfFTejVcGaCi2ewKKfeqXjwtVW+jNj34YzCaDLZ9Urj8C2W6N8CimSb c0tmozNkfKyFpYTR2nQ8MUQSWDkR9/k= ARC-Authentication-Results: i=1; imf08.hostedemail.com; dkim=pass header.d=rivosinc-com.20230601.gappssmtp.com header.s=20230601 header.b=sUPMyesV; dmarc=none; spf=pass (imf08.hostedemail.com: domain of debug@rivosinc.com designates 209.85.161.54 as permitted sender) smtp.mailfrom=debug@rivosinc.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1711687629; a=rsa-sha256; cv=none; b=katIqOlWyx5FjJ+aAJfdTUU3GjC08qNO4I3mt2JlggTRXRn2ceb3vV+WH4CFWLG9ACs+hL Xtd9m3/E6y+n8pIHE3GIyHmu9H5yl7zBIk1ENQDKtPrhjynbA+Z72J23MOoztjnmt344kv W72KGH/U1C6AQVoTcV+ycjYn85Bh+zk= Received: by mail-oo1-f54.google.com with SMTP id 006d021491bc7-5a4859178f1so1040348eaf.0 for ; Thu, 28 Mar 2024 21:47:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rivosinc-com.20230601.gappssmtp.com; s=20230601; t=1711687628; x=1712292428; darn=kvack.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=9MOz30J7VxjH8ZagxzRr7bVMOq1rQVKKUTnSRMNh/j0=; b=sUPMyesVJMMtbbUVSx2FNPUzcJfEpzp27LgoZ4TSXOr1x/UbDMXVim5qrfEIIutqXq fWlev5QrEk/xbiUuyRuuWT11qXxDhuuBqfNpDkzxcs/9lmgV5jjMc/2Zn4hVkn3RLhdZ GZCvMUFYUOSKsdu31Jesh8KZEFPAJNW4YFQ7IlZiWGzYYN5ywAlDf5E15ZBlgzfNlT9L XOzCOK7irJX8ezAiOoWE4+7/Wj1q9r1u1aXvlRUt46QBBo0RwBdKim/qRkHKhX5WdOzm rfzWSQlTrvjMj53STh0XnjUxOutdf6BHIy3B6Z95W/Dbl5xOarbkEuMUUkk6+1J5qese r28w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711687628; x=1712292428; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=9MOz30J7VxjH8ZagxzRr7bVMOq1rQVKKUTnSRMNh/j0=; b=D/vpNoA/r3YXZuXFxPlIqRPb7y8uoL+REIPp64hopO09uAcVUE1sPDXgj1FZ31ISp5 7ZfgWOtxh1K/nbfrUJoTd7YnASjcp+A3jXgaU6pMJ1FFx26UnIoodl9SsSNwVVfu8DeJ 3ZO/32o+gM23XflkLHa8QddJoxacYhznUCWkHhMr7veD4Ww+F6Oi4jV+Yd9kJq7dsgUO M591ohzZbqtpmSUyAifn4hTEUEApMlukbyYzqSFtKV1VhqhCt6+MauGO4PHQf9haMTIh zrwmy7MsQtgm0uK5YOrSin1GsKgoo/UyiN2YNmcgKfV0qPEn7h+p+hdWR+DSytSVFlCd 39nA== X-Forwarded-Encrypted: i=1; AJvYcCXDvmtN44zU8iOaVhIrmMrpgZEYHgmdzCCZ3/Pqqb4n528To9UKDfh7hantyDwsgZPWh4nQrnQ7SO2lRjt0un35BIk= X-Gm-Message-State: AOJu0YwOyUHzt3KxCciYUBftczRWU5kX2asqoRx3bd86Cw5hGrst+jS4 SsJ3Rd/fgfTlee54Myb80hbfEqpUPBJXDWp5RszEECtZgkDObXo77cQUcRZjLnk= X-Google-Smtp-Source: AGHT+IGB+y7twcpxmoV8AXjju7qFPWK1mID4DF6lwVek2eRahswiUwgjJa6zI5wt5U4lG69wDyeurg== X-Received: by 2002:a05:6871:410b:b0:22a:9e26:4789 with SMTP id la11-20020a056871410b00b0022a9e264789mr1115705oab.13.1711687628350; Thu, 28 Mar 2024 21:47:08 -0700 (PDT) Received: from debug.ba.rivosinc.com ([64.71.180.162]) by smtp.gmail.com with ESMTPSA id i18-20020aa78b52000000b006ea7e972947sm2217120pfd.130.2024.03.28.21.47.05 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 28 Mar 2024 21:47:07 -0700 (PDT) From: Deepak Gupta To: paul.walmsley@sifive.com, rick.p.edgecombe@intel.com, broonie@kernel.org, Szabolcs.Nagy@arm.com, kito.cheng@sifive.com, keescook@chromium.org, ajones@ventanamicro.com, conor.dooley@microchip.com, cleger@rivosinc.com, atishp@atishpatra.org, alex@ghiti.fr, bjorn@rivosinc.com, alexghiti@rivosinc.com, samuel.holland@sifive.com, palmer@sifive.com, conor@kernel.org, linux-doc@vger.kernel.org, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-mm@kvack.org, linux-arch@vger.kernel.org, linux-kselftest@vger.kernel.org Cc: corbet@lwn.net, tech-j-ext@lists.risc-v.org, palmer@dabbelt.com, aou@eecs.berkeley.edu, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, oleg@redhat.com, akpm@linux-foundation.org, arnd@arndb.de, ebiederm@xmission.com, Liam.Howlett@oracle.com, vbabka@suse.cz, lstoakes@gmail.com, shuah@kernel.org, brauner@kernel.org, debug@rivosinc.com, andy.chiu@sifive.com, jerry.shih@sifive.com, hankuan.chen@sifive.com, greentime.hu@sifive.com, evan@rivosinc.com, xiao.w.wang@intel.com, charlie@rivosinc.com, apatel@ventanamicro.com, mchitale@ventanamicro.com, dbarboza@ventanamicro.com, sameo@rivosinc.com, shikemeng@huaweicloud.com, willy@infradead.org, vincent.chen@sifive.com, guoren@kernel.org, samitolvanen@google.com, songshuaishuai@tinylab.org, gerg@kernel.org, heiko@sntech.de, bhe@redhat.com, jeeheng.sia@starfivetech.com, cyy@cyyself.name, maskray@google.com, ancientmodern4@gmail.com, mathis.salmen@matsal.de, cuiyunhui@bytedance.com, bgray@linux.ibm.com, mpe@ellerman.id.au, baruch@tkos.co.il, alx@kernel.org, david@redhat.com, catalin.marinas@arm.com, revest@chromium.org, josh@joshtriplett.org, shr@devkernel.io, deller@gmx.de, omosnace@redhat.com, ojeda@kernel.org, jhubbard@nvidia.com Subject: [PATCH v2 26/27] riscv: Documentation for shadow stack on riscv Date: Thu, 28 Mar 2024 21:44:58 -0700 Message-Id: <20240329044459.3990638-27-debug@rivosinc.com> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20240329044459.3990638-1-debug@rivosinc.com> References: <20240329044459.3990638-1-debug@rivosinc.com> MIME-Version: 1.0 X-Rspamd-Queue-Id: 6A7D1160012 X-Rspam-User: X-Rspamd-Server: rspam04 X-Stat-Signature: 8b7wie6nfdux5qw5i1umhtw3hgaiwu13 X-HE-Tag: 1711687629-652005 X-HE-Meta: U2FsdGVkX1+1yBrAXWitHphSqs+7AuISXOZgtqeTt98d1VI7ltqvfL6eNsMY06mvqGpF67gwfdaQOC0BzRpZ+riDBTg6Ex8X3Hw1RsVW62tfa566uMKusKvtuxgiB9NYFEVeK3hJAMMXsfpdkUHBCksFdQc6qu4eqsXdMd/V4Bf/R8uYtdyjM3i7ecgDrw6u3BsKp/54+40tIpow8QWBZ8PpIgs2RMdiAYdhgf/0t4HpDeRGV136op6yopAYccjD9GPFUTu6RF5cc6B2d/9Hxi6h9liW1p7QMNWDIkDt0MK6Pau45tNk8zCWKVsoTRv24yO8DDjQiGEv9mMQdzd2E9fGFE+f8WZIL2/y0g5kzzCMaybDVNt7334JBN3Nl2eX2I6+XvGRnGFyQm8eWamkDajmrP8mrqGid7GTyGcDyNqLlH6hSgzLu3zHPHnoHO9jsWiwbb2VHUvk2cjGY8isQ1w0FrTvCOMZg9OIXnDXxDp9bjNs0Oj0uyF5fXdFZj8FwGlwWkgFkPyJlynwexVbZZU96+SDz3/KHkNmWTxP3q7TKWFb3yN0vZm8O2mOCbKO9MSG/S530i0GhwkoEnf3HbhcG/ScbuT9tsPRj3NHwcnmB7SDDi24xSod9X6s1S87UHF/Dj0IhVd35PoB94Zi5PW3CPPhRS68xeYfEDfut5L9cdqj38iAIH+1vHKnC8/BXiBUgzlHBr1P9yK0X1qunmHLm81YtfY/XUrQii6X1ysitRB/czEr13dYpcBQ1c1SxOnavC/g7x70L/BVNk63mswEAhpGPnI104uBFupF+OP1gAYyHuVCVhBGMAU7LDKyJ7shfH5uaKistHvz4VEGOZcQV65cyuSXRFSlbYaQbxexvjcj+vVA2vDy4MHdHHc0N17kMSVMqOMIE0wTG/Zkq5YtaWIiTofcqGUjuHlkMQEeTixyWDeYwWVlwtUk9TDULiQbmc2i166pVsFl3iK udVkmSg+ AAf6xSWQrithECl6e5OdvRF4P/cEVQV2ZPwqCz33eTOwOGA4rDVAOB3UrkZ5gO16maCh3wMVMDb8SfLUq7RAi06P6qEf3e1j1EUagy0xROtdN1WXOLWQwvFbL34pUr5KxDRZ0PPKgCjw258Jzy/G0B++EJ/HW3ox9V0JDN6bu5qiAmQR50w7PJtctp+Xr6U6bxgXFutpf1q9I/TRiAJOAL6YftD83qOd/sxZXn21PM7bkqdk= X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: List-Subscribe: List-Unsubscribe: Adding documentation on shadow stack for user mode on riscv and kernel interfaces exposed so that user tasks can enable it. Signed-off-by: Deepak Gupta --- Documentation/arch/riscv/zicfiss.rst | 169 +++++++++++++++++++++++++++ 1 file changed, 169 insertions(+) create mode 100644 Documentation/arch/riscv/zicfiss.rst diff --git a/Documentation/arch/riscv/zicfiss.rst b/Documentation/arch/riscv/zicfiss.rst new file mode 100644 index 000000000000..f133b6af9c15 --- /dev/null +++ b/Documentation/arch/riscv/zicfiss.rst @@ -0,0 +1,169 @@ +.. SPDX-License-Identifier: GPL-2.0 + +:Author: Deepak Gupta +:Date: 12 January 2024 + +========================================================= +Shadow stack to protect function returns on RISC-V Linux +========================================================= + +This document briefly describes the interface provided to userspace by Linux +to enable shadow stack for user mode applications on RISV-V + +1. Feature Overview +-------------------- + +Memory corruption issues usually result in to crashes, however when in hands of +an adversary and if used creatively can result into variety security issues. + +One of those security issues can be code re-use attacks on program where adversary +can use corrupt return addresses present on stack and chain them together to perform +return oriented programming (ROP) and thus compromising control flow integrity (CFI) +of the program. + +Return addresses live on stack and thus in read-write memory and thus are +susceptible to corruption and allows an adversary to reach any program counter +(PC) in address space. On RISC-V `zicfiss` extension provides an alternate stack +`shadow stack` on which return addresses can be safely placed in prolog of the +function and retrieved in epilog. `zicfiss` extension makes following changes + + - PTE encodings for shadow stack virtual memory + An earlier reserved encoding in first stage translation i.e. + PTE.R=0, PTE.W=1, PTE.X=0 becomes PTE encoding for shadow stack pages. + + - `sspush x1/x5` instruction pushes (stores) `x1/x5` to shadow stack. + + - `sspopchk x1/x5` instruction pops (loads) from shadow stack and compares + with `x1/x5` and if un-equal, CPU raises `software check exception` with + `*tval = 3` + +Compiler toolchain makes sure that function prologs have `sspush x1/x5` to save return +address on shadow stack in addition to regular stack. Similarly function epilogs have +`ld x5, offset(x2)`; `sspopchk x5` to ensure that popped value from regular stack +matches with popped value from shadow stack. + +2. Shadow stack protections and linux memory manager +----------------------------------------------------- + +As mentioned earlier, shadow stack get new page table encodings and thus have some +special properties assigned to them and instructions that operate on them as below + + - Regular stores to shadow stack memory raises access store faults. + This way shadow stack memory is protected from stray inadvertant + writes + + - Regular loads to shadow stack memory are allowed. + This allows stack trace utilities or backtrace functions to read + true callstack (not tampered) + + - Only shadow stack instructions can generate shadow stack load or + shadow stack store. + + - Shadow stack load / shadow stack store on read-only memory raises + AMO/store page fault. Thus both `sspush x1/x5` and `sspopchk x1/x5` + will raise AMO/store page fault. This simplies COW handling in kernel + During fork, kernel can convert shadow stack pages into read-only + memory (as it does for regular read-write memory) and as soon as + subsequent `sspush` or `sspopchk` in userspace is encountered, then + kernel can perform COW. + + - Shadow stack load / shadow stack store on read-write, read-write- + execute memory raises an access fault. This is a fatal condition + because shadow stack should never be operating on read-write, read- + write-execute memory. + +3. ELF and psABI +----------------- + +Toolchain sets up `GNU_PROPERTY_RISCV_FEATURE_1_BCFI` for property +`GNU_PROPERTY_RISCV_FEATURE_1_AND` in notes section of the object file. + +4. Linux enabling +------------------ + +User space programs can have multiple shared objects loaded in its address space +and it's a difficult task to make sure all the dependencies have been compiled +with support of shadow stack. Thus it's left to dynamic loader to enable +shadow stack for the program. + +5. prctl() enabling +-------------------- + +`PR_SET_SHADOW_STACK_STATUS` / `PR_GET_SHADOW_STACK_STATUS` / +`PR_LOCK_SHADOW_STACK_STATUS` are three prctls added to manage shadow stack +enabling for tasks. prctls are arch agnostic and returns -EINVAL on other arches. + +`PR_SET_SHADOW_STACK_STATUS`: If arg1 `PR_SHADOW_STACK_ENABLE` and if CPU supports +`zicfiss` then kernel will enable shadow stack for the task. Dynamic loader can +issue this `prctl` once it has determined that all the objects loaded in address +space have support for shadow stack. Additionally if there is a `dlopen` to an +object which wasn't compiled with `zicfiss`, dynamic loader can issue this prctl +with arg1 set to 0 (i.e. `PR_SHADOW_STACK_ENABLE` being clear) + +`PR_GET_SHADOW_STACK_STATUS`: Returns current status of indirect branch tracking. +If enabled it'll return `PR_SHADOW_STACK_ENABLE` + +`PR_LOCK_SHADOW_STACK_STATUS`: Locks current status of shadow stack enabling on the +task. User space may want to run with strict security posture and wouldn't want +loading of objects without `zicfiss` support in it and thus would want to disallow +disabling of shadow stack on current task. In that case user space can use this prctl +to lock current settings. + +5. violations related to returns with shadow stack enabled +----------------------------------------------------------- + +Pertaining to shadow stack, CPU raises software check exception in following +condition + + - On execution of `sspopchk x1/x5`, x1/x5 didn't match top of shadow stack. + If mismatch happens then cpu does `*tval = 3` and raise software check + exception + +Linux kernel will treat this as `SIGSEV`` with code = `SEGV_CPERR` and follow +normal course of signal delivery. + +6. Shadow stack tokens +----------------------- +Regular stores on shadow stacks are not allowed and thus can't be tampered with via +arbitrary stray writes due to bugs. Method of pivoting / switching to shadow stack +is simply writing to csr `CSR_SSP` changes active shadow stack. This can be problematic +because usually value to be written to `CSR_SSP` will be loaded somewhere in writeable +memory and thus allows an adversary to corruption bug in software to pivot to an any +address in shadow stack range. Shadow stack tokens can help mitigate this problem by +making sure that: + + - When software is switching away from a shadow stack, shadow stack pointer should be + saved on shadow stack itself and call it `shadow stack token` + + - When software is switching to a shadow stack, it should read the `shadow stack token` + from shadow stack pointer and verify that `shadow stack token` itself is pointer to + shadow stack itself. + + - Once the token verification is done, software can perform the write to `CSR_SSP` to + switch shadow stack. + +Here software can be user mode task runtime itself which is managing various contexts +as part of single thread. Software can be kernel as well when kernel has to deliver a +signal to user task and must save shadow stack pointer. Kernel can perform similar +procedure by saving a token on user shadow stack itself. This way whenever sigreturn +happens, kernel can read the token and verify the token and then switch to shadow stack. +Using this mechanism, kernel helps user task so that any corruption issue in user task +is not exploited by adversary by arbitrarily using `sigreturn`. Adversary will have to +make sure that there is a `shadow stack token` in addition to invoking `sigreturn` + +7. Signal shadow stack +----------------------- +Following structure has been added to sigcontext for RISC-V. `rsvd` field has been kept +in case we need some extra information in future for landing pads / indirect branch +tracking. It has been kept today in order to allow backward compatibility in future. + +struct __sc_riscv_cfi_state { + unsigned long ss_ptr; + unsigned long rsvd; +}; + +As part of signal delivery, shadow stack token is saved on current shadow stack itself and +updated pointer is saved away in `ss_ptr` field in `__sc_riscv_cfi_state` under `sigcontext` +Existing shadow stack allocation is used for signal delivery. During `sigreturn`, kernel will +obtain `ss_ptr` from `sigcontext` and verify the saved token on shadow stack itself and switch +shadow stack.