From: Sascha Hauer <s.hauer@pengutronix.de>
To: Holger Schurig <holgerschurig@gmail.com>
Cc: barebox@lists.infradead.org, Holger Schurig <holgerschurig@gmail.de>
Subject: Re: [PATCH 1/3] lzo: properly check for overruns
Date: Wed, 2 Jul 2014 08:20:42 +0200 [thread overview]
Message-ID: <20140702062042.GA14257@pengutronix.de> (raw)
In-Reply-To: <1404249726-7663-1-git-send-email-holgerschurig@gmail.de>
On Tue, Jul 01, 2014 at 11:22:04PM +0200, Holger Schurig wrote:
> Note: this is the same as 206a81c18401c0cde6e579164f752c4b147324ce in
> linux-git.
>
> The lzo decompressor can, if given some really crazy data, possibly
> overrun some variable types. Modify the checking logic to properly
> detect overruns before they happen.
>
> Reported-by: "Don A. Bailey" <donb@securitymouse.com>
> Tested-by: "Don A. Bailey" <donb@securitymouse.com>
> Signed-off-by: Holger Schurig <holgerschurig@gmail.de>
> ---
> lib/lzo/lzo1x_decompress_safe.c | 64 +++++++++++++++++++++++++++--------------
> 1 file changed, 42 insertions(+), 22 deletions(-)
>
> diff --git a/lib/lzo/lzo1x_decompress_safe.c b/lib/lzo/lzo1x_decompress_safe.c
Applied all three lzx patches, thanks
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2014-07-02 6:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 21:22 Holger Schurig
2014-07-02 6:20 ` Sascha Hauer [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=20140702062042.GA14257@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=holgerschurig@gmail.com \
--cc=holgerschurig@gmail.de \
/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