[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180129.120124.892750865825553841.davem@davemloft.net>
Date: Mon, 29 Jan 2018 12:01:24 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: jasowang@...hat.com
Cc: mst@...hat.com, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, john.fastabend@...il.com
Subject: Re: [PATCH net-next] ptr_ring: fix integer overflow
From: Jason Wang <jasowang@...hat.com>
Date: Thu, 25 Jan 2018 15:31:42 +0800
> We try to allocate one more entry for lockless peeking. The adding
> operation may overflow which causes zero to be passed to kmalloc().
> In this case, it returns ZERO_SIZE_PTR without any notice by ptr
> ring. Try to do producing or consuming on such ring will lead NULL
> dereference. Fix this detect and fail early.
>
> Fixes: bcecb4bbf88a ("net: ptr_ring: otherwise safe empty checks can overrun array bounds")
> Reported-by: syzbot+87678bcf753b44c39b67@...kaller.appspotmail.com
> Cc: John Fastabend <john.fastabend@...il.com>
> Signed-off-by: Jason Wang <jasowang@...hat.com>
I'm dropping this because I am to understand that Michael Tsirkin's patch
series covers this issue.
Let me know if I still need to apply this.
Thanks.
Powered by blists - more mailing lists