From patchwork Fri Jan 12 14:19:29 2018 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Alexander Popov X-Patchwork-Id: 10161015 Return-Path: Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork.web.codeaurora.org (Postfix) with ESMTP id D9CB2602D8 for ; Fri, 12 Jan 2018 14:21:04 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id C63202898D for ; Fri, 12 Jan 2018 14:21:04 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id BAD7828990; Fri, 12 Jan 2018 14:21:04 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.2 required=2.0 tests=BAYES_00, RCVD_IN_DNSWL_MED autolearn=ham version=3.3.1 Received: from mother.openwall.net (mother.openwall.net [195.42.179.200]) by mail.wl.linuxfoundation.org (Postfix) with SMTP id C21092898D for ; Fri, 12 Jan 2018 14:21:03 +0000 (UTC) Received: (qmail 3987 invoked by uid 550); 12 Jan 2018 14:20:09 -0000 Mailing-List: contact kernel-hardening-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Delivered-To: mailing list kernel-hardening@lists.openwall.com Received: (qmail 3848 invoked from network); 12 Jan 2018 14:20:06 -0000 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:in-reply-to :references; bh=k+Xor7MdRQ/F+Vru095p3JqLE9jEZDmqmwZYJFYGqE0=; b=rV5IeJKPukUSe0co21OZBFQLEfTi38027gAYMr/ZLxLmJX00b0J7+Qn+gmNHyv8ZPf 9KoI0vFNjnij0K/5GokTKIUfK6xZBF7YO7x+uLLLRJGGY8UnH4V8J5q2i3rkVWWys7A6 Fz5fHFFr9Z7dQoCyL002vgYqo28sMoCdMpqOh8VBd5JT8SAjz56OW7OyTWbEDODY5It4 bR6LG5qHpO2TGEmzw7nWNMwYpfSeVtot6Gik/W2xmUa+C67C/zH5jqA1LloPCd+heVdE JyZnDiJjzKKCzBfQyoB/zOKTUQLPatW7/S/BcGE/c/3IYSxWStjZPv99UPF5pnqOwh5o qPSw== X-Gm-Message-State: AKwxytcmxmwL9b67kU623YeGbwIH9+NcWUlcXWock23nXNP6sSiwXKPu WNPOREYpjXA3yNmxICyKIrcDVZVZuUA= X-Google-Smtp-Source: ACJfBoviB4yV4UvhMbbSM5sWXSNUXCKE+YUv3y4Z/5ksDuL48qh7N2jvUdHCSwH5oB10ACFm8Mc0hA== X-Received: by 10.46.43.26 with SMTP id q26mr1372696lje.142.1515766794869; Fri, 12 Jan 2018 06:19:54 -0800 (PST) From: Alexander Popov To: kernel-hardening@lists.openwall.com, Kees Cook , PaX Team , Brad Spengler , Ingo Molnar , Andy Lutomirski , Tycho Andersen , Laura Abbott , Mark Rutland , Ard Biesheuvel , Borislav Petkov , Thomas Gleixner , "H . Peter Anvin" , Peter Zijlstra , "Dmitry V . Levin" , x86@kernel.org, alex.popov@linux.com Date: Fri, 12 Jan 2018 17:19:29 +0300 Message-Id: <1515766769-9120-7-git-send-email-alex.popov@linux.com> X-Mailer: git-send-email 2.7.4 In-Reply-To: <1515766769-9120-1-git-send-email-alex.popov@linux.com> References: <1515766769-9120-1-git-send-email-alex.popov@linux.com> Subject: [kernel-hardening] [PATCH RFC v7 6/6] doc: self-protection: Add information about STACKLEAK feature X-Virus-Scanned: ClamAV using ClamSMTP Add information about STACKLEAK feature to "Stack depth overflow" and "Memory poisoning" sections of self-protection.rst. Signed-off-by: Alexander Popov --- Documentation/security/self-protection.rst | 23 ++++++++++++++--------- 1 file changed, 14 insertions(+), 9 deletions(-) diff --git a/Documentation/security/self-protection.rst b/Documentation/security/self-protection.rst index 60c8bd8..9693a90 100644 --- a/Documentation/security/self-protection.rst +++ b/Documentation/security/self-protection.rst @@ -165,10 +165,15 @@ Stack depth overflow A less well understood attack is using a bug that triggers the kernel to consume stack memory with deep function calls or large stack allocations. With this attack it is possible to write beyond the end of -the kernel's preallocated stack space and into sensitive structures. Two -important changes need to be made for better protections: moving the -sensitive thread_info structure elsewhere, and adding a faulting memory -hole at the bottom of the stack to catch these overflows. +the kernel's preallocated stack space and into sensitive structures. +The combination of the following measures gives better protection: + +* moving the sensitive thread_info structure off the stack + (``CONFIG_THREAD_INFO_IN_TASK``); +* adding a faulting memory hole at the bottom of the stack to catch + these overflows (``CONFIG_VMAP_STACK``); +* runtime checking that alloca() calls don't overstep the stack boundary + (``CONFIG_GCC_PLUGIN_STACKLEAK``). Heap memory integrity --------------------- @@ -287,11 +292,11 @@ sure structure holes are cleared. Memory poisoning ---------------- -When releasing memory, it is best to poison the contents (clear stack on -syscall return, wipe heap memory on a free), to avoid reuse attacks that -rely on the old contents of memory. This frustrates many uninitialized -variable attacks, stack content exposures, heap content exposures, and -use-after-free attacks. +When releasing memory, it is best to poison the contents, to avoid reuse +attacks that rely on the old contents of memory. E.g., clear stack on a +syscall return (``CONFIG_GCC_PLUGIN_STACKLEAK``), wipe heap memory on a +free. This frustrates many uninitialized variable attacks, stack content +exposures, heap content exposures, and use-after-free attacks. Destination tracking --------------------