From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-9.9 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id BE558C4727F for ; Fri, 25 Sep 2020 20:28:35 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 26890206FC for ; Fri, 25 Sep 2020 20:28:35 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="MEf//uPe"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="XNId8adn" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 26890206FC Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=chromium.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=merlin.20170209; h=Sender:Content-Transfer-Encoding: Content-Type:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References:Message-ID: Subject:To:From:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=4D5k21BmQsHXpYzctXds1AObAJ3h/OHroUjOhbbulI8=; b=MEf//uPe5wx7DyHRTTjU3F9X9 U8G54ABOc0LNMgkj51VmBz7GmFAud92UtOqTjpxdkR4F22EUZPHZiR0Q0Klo6CtWEkYUm9Dl3tt+s Q+h+NgXq+FzV3AJZKer0DkMjFIrQAgCuq3YGN5dx8GqGgFh+kXer3SRHbYRV/Z+nkv1fWH1DXjmve gMboL6/8S8c0mFqsP5Hqcncruv6sqrBw5XDxsmfwJ7VK00W5VFtCsTRnt5/fdNk7g6ROy3VQei6bi aEs9ZDrFD7FoWXrpKIugAi8PcpqCfJyWNNlI5sD8f2yLq3atr7qxeDVwOe8RfXLw84B3hBqZE+kHe sPEh21ExA==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1kLuIp-00054W-Fz; Fri, 25 Sep 2020 20:26:47 +0000 Received: from mail-pg1-x544.google.com ([2607:f8b0:4864:20::544]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1kLuIm-000547-Hz for linux-arm-kernel@lists.infradead.org; Fri, 25 Sep 2020 20:26:45 +0000 Received: by mail-pg1-x544.google.com with SMTP id l71so3545790pge.4 for ; Fri, 25 Sep 2020 13:26:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=Fvm57bum9kABDubOAKIbQd4nwdbZ7F2cf8tIZTaBPm8=; b=XNId8adnBwEC06gRrqP/D3oaJauLEoxwFtxl+nQG3+ll1hkht6e5jd425rRVzwvmhW UbA7Hm/OAXHe+FDpDbPoiyhBxaAb6pU0fEoasNt6YJMYhm1HphELCt4XTXgO+ZeYVnJn e+1Dhh9NOdzaJBRh00ic7DJ0oj8EBbG9YZ/PE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=Fvm57bum9kABDubOAKIbQd4nwdbZ7F2cf8tIZTaBPm8=; b=HpbZlzAxOLoj2NQycwsLtZfk33JiH2B7CluUPVWZEavlAUXRjAXxi1euxCYA7igc6I l2RB5JTMBtWwMhhwPLCfSHjiiPrJOni21FProD03EfUGTlnfLktaBh3l1aLYzNXyJWhA 6pt9pd/BDiyGltNSYOkjNacMvoOmcOC1ysBUmMqsGbjDiuSn19pu1pqCAJAWY5rmUKkw UJwSEWvRROOlQLlNL/aW4PxoJfVHSjnefqQwQV3OLjHj+S4YhV0C+F4qsEHg1Yrwtpeu LAqMNw3QJ5du+zOwGtE4fa0lMJqDHPX018L/WwU6ySZUjMqOyNTc7vLZajzG6O+sVAyn xQ6A== X-Gm-Message-State: AOAM530lmuJ8rPCSvzz1KoTyxthIrppF2rHLUGjQTxU8hckwrAWPFNdH rq6g/aytTFv8g9foEQSSXxSl6g== X-Google-Smtp-Source: ABdhPJzHcUOsSX4WD1whW8SuAJtKoqgb4PqzG4KokfYygfdUFgfIAzjY6l1h6pQzMv383WEMuYRsog== X-Received: by 2002:a65:5881:: with SMTP id d1mr542082pgu.193.1601065600492; Fri, 25 Sep 2020 13:26:40 -0700 (PDT) Received: from www.outflux.net (smtp.outflux.net. [198.145.64.163]) by smtp.gmail.com with ESMTPSA id q15sm68096pje.29.2020.09.25.13.26.39 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 25 Sep 2020 13:26:39 -0700 (PDT) Date: Fri, 25 Sep 2020 13:26:38 -0700 From: Kees Cook To: Pintu Agarwal Subject: Re: KASLR support on ARM with Kernel 4.9 and 4.14 Message-ID: <202009251301.A1FD183582@keescook> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20200925_162644_630777_A138DAFB X-CRM114-Status: GOOD ( 25.75 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Mark Rutland , arnd@arndb.de, ard.biesheuvel@linaro.org, marc.zyngier@arm.com, dave.martin@arm.com, Kernelnewbies , Russell King - ARM Linux , open list , tony@atomide.com, matt@codeblueprint.co.uk, nico@linaro.org, thgarnie@google.com, "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Fri, Sep 25, 2020 at 08:33:59PM +0530, Pintu Agarwal wrote: > This is regarding the KASLR feature support on ARM for the kernel > version 4.9 and 4.14. > > Is KASLR supported on ARM-32 Linux 4.9 and above ? Sorry, this feature did not yet land in upstream: https://github.com/KSPP/linux/issues/3 Here was the earlier effort: https://lore.kernel.org/kernel-hardening/20170814125411.22604-1-ard.biesheuvel@linaro.org/ > Is it dependent on CONFIG_RANDOMIZE_BASE or CONFIG_RANDOMIZE_BASE is what is used on other architectures to control the feature. > /proc/sys/kernel/randomize_va_space ? > Is there any relation between these two? No, the latter is about userspace addresses. > Is the changing kernel symbols (in every boot), only possible if KASLR > is enabled, or there is another way it can happen? I think you meant kernel symbol addresses (not the symbols themselves). But yes, I wouldn't expect the addresses to move if you didn't either rebuild the kernel or had something else moving the kernel at boot (i.e. the boot loader). > I have these queries because, > In one of the arm-32 devices with Kernel 4.14, I observed that > CONFIG_RANDOMIZE_BASE is not available. > But /proc/sys/kernel/randomize_va_space is set to 2. > However, I also observed that symbol addresses are changing in every boot. > > 1st boot cycle: > [root ~]# cat /proc/kallsyms | grep "sys_open" > a5b4de92 T sys_open > [root@sa515m ~]# > > 2nd boot cycle: > [root ~]# cat /proc/kallsyms | grep "sys_open" > f546ed66 T sys_open > > So, I am wondering how this is possible without KASLR > (CONFIG_RANDOMIZE_BASE) support in Kernel ? What device is this? Is it a stock kernel? > Similarly, with Kernel 4.9 and CONFIG_RANDOMIZE_BASE is not available > but /proc/sys/kernel/randomize_va_space is set to 2. > But here, the addresses are remaining same. > > 1st Run: > [root~]# cat /proc/kallsyms | grep "sys_open" > c01ed68c T sys_open > [root ~]# > > *** reboot *** > [root ~]# cat /proc/kallsyms | grep "sys_open" > c01ed68c T sys_open > > > Is there any other difference between these two kernel versions with > respect to changing symbol addresses ? Is the boot loader changing the base address? (What boot loader are you using?) -- Kees Cook _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel