[Lucid][CVE-2014-4608]PATCH 0/3] lzo: properly check for overruns

[Luis Henriques]

Luis Henriques <luis.henriques at canonical.com> writes:

>> On a quick inspection it is hard to tell what it is consumed by sadly.
>> But worth spending half an hour checking.
>> 
>> -apw
>
> A quick 'git grep' shows that there are two consumers of functions
> lzo1x_1_compress() and lzo1x_decompress_safe(): fs/jffs2 and
> ubuntu/compcache.
>
> Looks like this last module (ramzswap) allows to run a quick test
> verify LZO isn't broken.  I'll do the following:
>
> 1. Run a Lucid system and enable a /dev/ramzswap0 device as the only
>    swap device for the system (disabling any other swap device set by
>    default on boot)
>
> 2. Load the system so that swap is used
>
> 3. Reduce the load so that swap space is back to 0
>
> 4. Do 2 and 3 for a while
>
> I'll report back later after running this test for a while.
>
> Cheers,
> --
> Luís

Ok, I've built a Lucid test kernel containing these 3 patches and
executed the test case described above.  I was able fill 100% of the
ramzswap device several times without any error/warning in the
kernel.

If this doesn't proof I'm not breaking LZO, at least it increases my
confidence on the patches :-)

Cheers,
-- 
Luís