From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754915Ab3LMWrV (ORCPT ); Fri, 13 Dec 2013 17:47:21 -0500 Received: from mail-pb0-f51.google.com ([209.85.160.51]:36606 "EHLO mail-pb0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754295Ab3LMWrS (ORCPT ); Fri, 13 Dec 2013 17:47:18 -0500 Message-ID: <52AB8F02.6030101@gmail.com> Date: Sat, 14 Dec 2013 09:49:38 +1100 From: Ryan Mallon User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.28) Gecko/20120313 Thunderbird/3.1.20 MIME-Version: 1.0 To: Vegard Nossum CC: Kees Cook , "Theodore Ts'o" , LKML , Tommi Rantala , Ingo Molnar , "Eric W. Biederman" , Andy Lutomirski , Daniel Vetter , Alan Cox , Greg Kroah-Hartman , Jason Wang , "David S. Miller" , Dan Carpenter , James Morris Subject: Re: [PATCH 1/9] Known exploit detection References: <1386867152-24072-1-git-send-email-vegard.nossum@oracle.com> <20131212190659.GG13547@thunk.org> <52AA4BC8.1080207@gmail.com> <52AAD178.6020607@oracle.com> In-Reply-To: <52AAD178.6020607@oracle.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 13/12/13 20:20, Vegard Nossum wrote: > On 12/13/2013 12:50 AM, Ryan Mallon wrote: >> On 13/12/13 08:13, Kees Cook wrote: >>> On Thu, Dec 12, 2013 at 11:06 AM, Theodore Ts'o wrote: >>>> On Thu, Dec 12, 2013 at 05:52:24PM +0100, vegard.nossum@oracle.com wrote: >>>>> The idea is simple -- since different kernel versions are vulnerable to >>>>> different root exploits, hackers most likely try multiple exploits before >>>>> they actually succeed. >> >> The _exploit() notifications could also be used to spam the syslogs. >> Although they are individually ratelimited, if there are enough >> _exploit() markers in the kernel then an annoying person can cycle >> through them all to generate large amounts of useless syslog. > > They are rate limited collectively, not individually, so this should not be an issue. Yes, sorry, I misread the code. I wonder if the exploit() function name should be changed though. Having: exploit("CVE-xxxx"); In the code looks like some sort of injection/testing framework. Maybe: warn_known_exploit("CVE-xxxx"); would be clearer? ~Ryan