On Mon, Apr 20, 2015 at 03:26:48PM +0800, Herbert Xu wrote:
> OK I have reviewed this and indeed it does appear that the bug
> can be triggered. The trick appears to be making sure that your
> input packet is fragmented. That should then activate the kmalloc
> path and lead to the memory corrupti
On Mon, Apr 20, 2015 at 09:17:22AM +0200, Romain Francoise wrote:
>
> For example, here's a photo I took of the crash on 3.18.4:
>
> https://orebokech.com/tmp/IMG_20150129_181653.jpg
OK I have reviewed this and indeed it does appear that the bug
can be triggered. The trick appears to be making
Hi Ben,
On Sun, Apr 19, 2015 at 03:15:35PM +0100, Ben Hutchings wrote:
> However, the upstream developers tell me that in this particular case
> the buffers will always have some extra padding that makes the
> overflows harmless in practice.
>
> Have you actually tested that this commit fixes the
Control: tag -1 moreinfo
On Tue, 14 Apr 2015 10:44:22 +0200 Romain Francoise
wrote:
> Package: src:linux
> Version: 3.16.7-ckt7-1
> Severity: wishlist
>
> Using the rfc4106 IPsec implementation provided by the aesni_intel
> module results in occasional crashes on an busy gateway. This was fixed
Package: src:linux
Version: 3.16.7-ckt7-1
Severity: wishlist
Using the rfc4106 IPsec implementation provided by the aesni_intel
module results in occasional crashes on an busy gateway. This was fixed
upstream by commit ccfe8c3f7e52:
| commit ccfe8c3f7e52ae83155cb038753f4c75b774ca8a
| Author: Step
5 matches
Mail list logo