From: Joe Perches <joe@perches.com>
To: "Tobin C. Harding" <me@tobin.cc>, kernel-hardening@lists.openwall.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lib/vsprintf: add default case to 'i' specifier
Date: Tue, 10 Oct 2017 00:09:35 -0700 [thread overview]
Message-ID: <1507619375.3552.28.camel@perches.com> (raw)
In-Reply-To: <1507517945-27155-1-git-send-email-me@tobin.cc>
On Mon, 2017-10-09 at 13:59 +1100, Tobin C. Harding wrote:
> %pi leaks kernel addresses if incorrectly specified.
Are there any uses that are incorrectly specified?
grep doesn't show any.
> Currently the printk specifier %pi (%pI) contains a switch statement
> without a default clause. The %pi specifier requires a subsequent
> character (4, 6, or S) controlling the output. If the specifier is
> incomplete the switch statement will fall through and print the variable
> argument address in hex instead of the value of the argument (as an IP
> address).
>
> If uncaught this leaks kernel addresses into dmesg. We can return an
> error string to make the bug visible and stop addresses leaking.
>
> Add a default clause returning an error string, stops leaking addresses
> and makes the buggy code
[]
> diff --git a/lib/vsprintf.c b/lib/vsprintf.c
[]
> @@ -1775,6 +1775,8 @@ char *pointer(const char *fmt, char *buf, char *end, void *ptr,
> default:
> return string(buf, end, "(invalid address)", spec);
> }}
> + default:
> + return string(buf, end, "(invalid specifier, form: %pi4)", spec);
> }
> break;
> case 'E':
I'm not sure this is a big deal and
maybe a better way to handle it is to
move the %pK, case 'K': block and add
a fallthrough or keep the case 'K':
block where it is and add a goto.
next prev parent reply other threads:[~2017-10-10 7:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 2:59 [PATCH] lib/vsprintf: add default case to 'i' specifier Tobin C. Harding
2017-10-09 15:16 ` [kernel-hardening] " Tycho Andersen
2017-10-09 21:27 ` Tobin C. Harding
2017-10-10 7:09 ` Joe Perches [this message]
2017-10-10 21:47 ` Tobin C. Harding
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=1507619375.3552.28.camel@perches.com \
--to=joe@perches.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=me@tobin.cc \
/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