From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nicolas Iooss <nicolas.iooss_linux@m4x.org>
Cc: Felipe Balbi <balbi@ti.com>, Joel Becker <jlbec@evilplan.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] configfs: fix kernel infoleak through user-controlled format string
Date: Tue, 7 Jul 2015 15:34:48 -0700 [thread overview]
Message-ID: <20150707223448.GA30548@kroah.com> (raw)
In-Reply-To: <1436279280-28492-2-git-send-email-nicolas.iooss_linux@m4x.org>
On Tue, Jul 07, 2015 at 10:28:00PM +0800, Nicolas Iooss wrote:
> Some modules call config_item_init_type_name() and
> config_group_init_type_name() with parameter "name" directly controlled
> by userspace. These two functions call config_item_set_name() with this
> name used as a format string, which can be used to leak information such
> as content of the stack to userspace.
>
> For example, make_netconsole_target() in netconsole module calls
> config_item_init_type_name() with the name of a newly-created directory.
> This means that the following commands give some unexpected output, with
> configfs mounted in /sys/kernel/config/ and on a system with a
> configured eth0 ethernet interface:
>
> # modprobe netconsole
> # mkdir /sys/kernel/config/netconsole/target_%lx
> # echo eth0 > /sys/kernel/config/netconsole/target_%lx/dev_name
> # echo 1 > /sys/kernel/config/netconsole/target_%lx/enabled
> # echo eth0 > /sys/kernel/config/netconsole/target_%lx/dev_name
> # dmesg |tail -n1
> [ 142.697668] netconsole: target (target_ffffffffc0ae8080) is
> enabled, disable to update parameters
>
> The directory name is correct but %lx has been interpreted in the
> internal item name, displayed here in the error message used by
> store_dev_name() in drivers/net/netconsole.c.
>
> To fix this, update every caller of config_item_set_name to use "%s"
> when operating on untrusted input.
>
> This issue was found using -Wformat-security gcc flag, once a __printf
> attribute has been added to config_item_set_name().
>
> Signed-off-by: Nicolas Iooss <nicolas.iooss_linux@m4x.org>
> ---
> drivers/usb/gadget/configfs.c | 2 +-
> fs/configfs/item.c | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
Nice catch:
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
prev parent reply other threads:[~2015-07-07 22:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 14:27 [PATCH 1/2] include, lib: add __printf attributes to several function prototypes Nicolas Iooss
2015-07-07 14:28 ` [PATCH 2/2] configfs: fix kernel infoleak through user-controlled format string Nicolas Iooss
2015-07-07 17:39 ` Felipe Balbi
2015-07-07 22:34 ` Greg Kroah-Hartman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150707223448.GA30548@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=balbi@ti.com \
--cc=jlbec@evilplan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.iooss_linux@m4x.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox