On Tue, May 28, 2019 at 5:56 PM Greg KH wrote:
>
> On Tue, May 28, 2019 at 05:14:21PM -0700, Christoph Paasch wrote:
> > On 28/05/19 - 17:07:44, Greg KH wrote:
> > > On Tue, May 28, 2019 at 05:01:13PM -0700, Christoph Paasch wrote:
> > > > When building the erspan header for either v1 or v2, the e
On Tue, May 28, 2019 at 05:14:21PM -0700, Christoph Paasch wrote:
> On 28/05/19 - 17:07:44, Greg KH wrote:
> > On Tue, May 28, 2019 at 05:01:13PM -0700, Christoph Paasch wrote:
> > > When building the erspan header for either v1 or v2, the eth_hdr()
> > > does not point to the right inner packet's
On 28/05/19 - 17:07:44, Greg KH wrote:
> On Tue, May 28, 2019 at 05:01:13PM -0700, Christoph Paasch wrote:
> > When building the erspan header for either v1 or v2, the eth_hdr()
> > does not point to the right inner packet's eth_hdr,
> > causing kasan report use-after-free and slab-out-of-bouds rea
On Tue, May 28, 2019 at 05:01:13PM -0700, Christoph Paasch wrote:
> When building the erspan header for either v1 or v2, the eth_hdr()
> does not point to the right inner packet's eth_hdr,
> causing kasan report use-after-free and slab-out-of-bouds read.
>
> The patch fixes the following syzkaller