Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755702AbbLGJxH (ORCPT ); Mon, 7 Dec 2015 04:53:07 -0500 Received: from mga02.intel.com ([134.134.136.20]:35544 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755024AbbLGJxF (ORCPT ); Mon, 7 Dec 2015 04:53:05 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,394,1444719600"; d="scan'208";a="868192584" From: Jani Nikula To: Daniel Vetter , Nicolas Iooss Cc: Terje =?utf-8?Q?Bergstr=C3=B6m?= , Alison Wang , linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, linux-tegra@vger.kernel.org Subject: Re: [PATCH] drm: do not use device name as a format string In-Reply-To: <20151207074312.GU10243@phenom.ffwll.local> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo References: <1447869498-13277-1-git-send-email-nicolas.iooss_linux@m4x.org> <5662B24E.4090202@m4x.org> <20151206093559.GT10243@phenom.ffwll.local> <56640B00.7040100@m4x.org> <20151207074312.GU10243@phenom.ffwll.local> User-Agent: Notmuch/0.20.2+101~gb57168b (http://notmuchmail.org) Emacs/24.4.1 (x86_64-pc-linux-gnu) Date: Mon, 07 Dec 2015 11:53:01 +0200 Message-ID: <874mfuzite.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2581 Lines: 56 On Mon, 07 Dec 2015, Daniel Vetter wrote: > On Sun, Dec 06, 2015 at 11:16:32AM +0100, Nicolas Iooss wrote: >> On 12/06/2015 10:35 AM, Daniel Vetter wrote: >> >> On 11/18/2015 06:58 PM, Nicolas Iooss wrote: >> >>> drm_dev_set_unique() formats its parameter using kvasprintf() but many >> >>> of its callers directly pass dev_name(dev) as printf format string, >> >>> without any format parameter. This can cause some issues when the >> >>> device name contains '%' characters. >> >>> >> >>> To avoid any potential issue, always use "%s" when using >> >>> drm_dev_set_unique() with dev_name(). >> > >> > Not sure this is worth it really, normally people don't place % characters >> > into their device names, ever. And if they do it'll blow up. There's also >> > no security issue here since userspace can't set this name. >> > >> > If the maintainers of the affected drivers don't want this I won't merge >> > this patch. >> >> Actually I had the same opinion before I began to add __printf >> attributes and "%s" in several places in the kernel to make >> -Wformat-security useful. This led me to discover some funny issues >> like the one fixed by commit 3958b79266b1 ("configfs: fix kernel >> infoleak through user-controlled format string", >> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=3958b79266b14729edd61daf9dfb84de45f4ec6d >> ). The patch I sent is in fact a very small step towards making >> -Wformat-security useful again to detect "real" issues. >> >> Of course, if you do not feel it is worth it and believe that dev_name >> is fully controlled by trusted sources which will never introduce any % >> character, I understand your will of not merging my patch. > > Ah, that's the context I was missing, that really should be in the commit > message. If this is part of an overall effort to enable something useful > it makes more sense to get it in. > > On the patch itself it feels rather funny to do a "%s", str); combo, maybe > we should have a drm_dev_set_unique_static instead? Including kerneldoc > explaining why there's too. No caller of drm_dev_set_unique() actually uses the formatting for anything... so you'd end up with drm_dev_set_unique_static() and an orphaned drm_dev_set_unique()... BR, Jani. -- Jani Nikula, Intel Open Source Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/