From: Eric Biggers <ebiggers3@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, keyrings@vger.kernel.org,
mark.rutland@arm.com, ebiggers@google.com
Subject: Re: [PATCH RESEND net-next v2] KEYS: DNS: limit the length of option strings
Date: Tue, 17 Apr 2018 18:23:40 +0000 [thread overview]
Message-ID: <20180417182340.GB9237@gmail.com> (raw)
In-Reply-To: <20180417.134316.1413649044013070735.davem@davemloft.net>
On Tue, Apr 17, 2018 at 01:43:16PM -0400, David Miller wrote:
> From: Eric Biggers <ebiggers3@gmail.com>
> Date: Mon, 16 Apr 2018 14:29:22 -0700
>
> > From: Eric Biggers <ebiggers@google.com>
> >
> > Adding a dns_resolver key whose payload contains a very long option name
> > resulted in that string being printed in full. This hit the WARN_ONCE()
> > in set_precision() during the printk(), because printk() only supports a
> > precision of up to 32767 bytes:
> >
> > precision 1000000 too large
> > WARNING: CPU: 0 PID: 752 at lib/vsprintf.c:2189 vsnprintf+0x4bc/0x5b0
> >
> > Fix it by limiting option strings (combined name + value) to a much more
> > reasonable 128 bytes. The exact limit is arbitrary, but currently the
> > only recognized option is formatted as "dnserror=%lu" which fits well
> > within this limit.
> >
> > Also ratelimit the printks.
> >
> > Reproducer:
> >
> > perl -e 'print "#", "A" x 1000000, "\x00"' | keyctl padd dns_resolver desc @s
> >
> > This bug was found using syzkaller.
> >
> > Reported-by: Mark Rutland <mark.rutland@arm.com>
> > Fixes: 4a2d789267e0 ("DNS: If the DNS server returns an error, allow that to be cached [ver #2]")
> > Signed-off-by: Eric Biggers <ebiggers@google.com>
>
> Applied, thanks.
Can you queue this up for stable too? syzbot has been hitting this on older
kernel versions.
Eric
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers3@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, keyrings@vger.kernel.org,
mark.rutland@arm.com, ebiggers@google.com
Subject: Re: [PATCH RESEND net-next v2] KEYS: DNS: limit the length of option strings
Date: Tue, 17 Apr 2018 11:23:40 -0700 [thread overview]
Message-ID: <20180417182340.GB9237@gmail.com> (raw)
In-Reply-To: <20180417.134316.1413649044013070735.davem@davemloft.net>
On Tue, Apr 17, 2018 at 01:43:16PM -0400, David Miller wrote:
> From: Eric Biggers <ebiggers3@gmail.com>
> Date: Mon, 16 Apr 2018 14:29:22 -0700
>
> > From: Eric Biggers <ebiggers@google.com>
> >
> > Adding a dns_resolver key whose payload contains a very long option name
> > resulted in that string being printed in full. This hit the WARN_ONCE()
> > in set_precision() during the printk(), because printk() only supports a
> > precision of up to 32767 bytes:
> >
> > precision 1000000 too large
> > WARNING: CPU: 0 PID: 752 at lib/vsprintf.c:2189 vsnprintf+0x4bc/0x5b0
> >
> > Fix it by limiting option strings (combined name + value) to a much more
> > reasonable 128 bytes. The exact limit is arbitrary, but currently the
> > only recognized option is formatted as "dnserror=%lu" which fits well
> > within this limit.
> >
> > Also ratelimit the printks.
> >
> > Reproducer:
> >
> > perl -e 'print "#", "A" x 1000000, "\x00"' | keyctl padd dns_resolver desc @s
> >
> > This bug was found using syzkaller.
> >
> > Reported-by: Mark Rutland <mark.rutland@arm.com>
> > Fixes: 4a2d789267e0 ("DNS: If the DNS server returns an error, allow that to be cached [ver #2]")
> > Signed-off-by: Eric Biggers <ebiggers@google.com>
>
> Applied, thanks.
Can you queue this up for stable too? syzbot has been hitting this on older
kernel versions.
Eric
next prev parent reply other threads:[~2018-04-17 18:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 21:29 [PATCH RESEND net-next v2] KEYS: DNS: limit the length of option strings Eric Biggers
2018-04-16 21:29 ` Eric Biggers
2018-04-17 17:43 ` David Miller
2018-04-17 17:43 ` David Miller
2018-04-17 18:23 ` Eric Biggers [this message]
2018-04-17 18:23 ` Eric Biggers
2018-04-17 18:24 ` David Miller
2018-04-17 18:24 ` David Miller
2018-04-17 18:37 ` Eric Biggers
2018-04-17 18:37 ` Eric Biggers
2018-04-17 18:52 ` David Miller
2018-04-17 18:52 ` David Miller
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=20180417182340.GB9237@gmail.com \
--to=ebiggers3@gmail.com \
--cc=davem@davemloft.net \
--cc=ebiggers@google.com \
--cc=keyrings@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.