From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751868AbdL0Mor (ORCPT ); Wed, 27 Dec 2017 07:44:47 -0500 Received: from mail-wr0-f193.google.com ([209.85.128.193]:36109 "EHLO mail-wr0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750967AbdL0Moo (ORCPT ); Wed, 27 Dec 2017 07:44:44 -0500 X-Google-Smtp-Source: ACJfBovNI4DgR0GcCWEB29k1G1XlyGj9agaR51KtC2KDwjeREarDt+dZHL40qyJaXqhjxkQqB+ZwGQ== From: Dmitry Vyukov To: akpm@linux-foundation.org, aryabinin@virtuozzo.com Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, kasan-dev@googlegroups.com, Dmitry Vyukov Subject: [PATCH 0/5] kasan: detect invalid frees Date: Wed, 27 Dec 2017 13:44:31 +0100 Message-Id: X-Mailer: git-send-email 2.15.1.620.gb9897f4670-goog Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org KASAN detects double-frees, but does not detect invalid-frees (when a pointer into a middle of heap object is passed to free). We recently had a very unpleasant case in crypto code which freed an inner object inside of a heap allocation. This left unnoticed during free, but totally corrupted heap and later lead to a bunch of random crashes all over kernel code. Detect invalid frees. Dmitry Vyukov (5): kasan: detect invalid frees for large objects kasan: don't use __builtin_return_address(1) kasan: detect invalid frees for large mempool objects kasan: unify code between kasan_slab_free() and kasan_poison_kfree() kasan: detect invalid frees include/linux/kasan.h | 13 ++++---- lib/test_kasan.c | 83 +++++++++++++++++++++++++++++++++++++++++++++++++++ mm/kasan/kasan.c | 57 +++++++++++++++++++---------------- mm/kasan/kasan.h | 3 +- mm/kasan/report.c | 5 ++-- mm/mempool.c | 6 ++-- mm/slab.c | 6 ++-- mm/slub.c | 10 +++---- 8 files changed, 135 insertions(+), 48 deletions(-) -- 2.15.1.620.gb9897f4670-goog