[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160128141557.74ad75f0@lxorguk.ukuu.org.uk>
Date: Thu, 28 Jan 2016 14:15:57 +0000
From: One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
To: Eric Dumazet <eric.dumazet@...il.com>
Cc: Zhouyi Zhou <yizhouzhou@....ac.cn>,
Zhouyi Zhou <zhouzhouyi@...il.com>, pablo@...filter.org,
kaber@...sh.net, kadlec@...ckhole.kfki.hu, davem@...emloft.net,
netfilter-devel@...r.kernel.org, coreteam@...filter.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH V2] netfilter: h323: avoid potential attack
On Thu, 28 Jan 2016 06:00:50 -0800
Eric Dumazet <eric.dumazet@...il.com> wrote:
> On Thu, 2016-01-28 at 21:14 +0800, Zhouyi Zhou wrote:
>
> > My patch is intend to prevent kernel panic, to prevent reading garbage
> > or read data from a prior frame and leak secrets, the prototypes of the
> > get_h2x5_addr functions and the functions that call get_h2x5_addr should
> > be changed, should we do this?
>
> In term of security, panics are better than allowing attacker to read
> data from other people, like a password.
>
> BTW, are you able to trigger any panic ?
We have a smattering of panics in this code in bugzilla going back years.
https://bugzilla.kernel.org/show_bug.cgi?id=12473
etc
Alan
Powered by blists - more mailing lists