'skb' buffer address information leakage

Hi all: I'd found several address leaks of "skb" buffer.When i have a arbitrary address write vulnerability in kernel(enabled kASLR),I can use skb's address find sk_destruct's address and overwrite it. And then,invoke close(sock_fd) function can trigger the shellcode(sk_destruct func). In kernel 4

Possible DEADLOCK in rtnl_lock(v4.1.40)

Hi: I've got the following error report while fuzzing the kernel with syzkaller on v4.1.40 Syzkaller hit 'possible deadlock in rtnl_lock' bug on commit . The guilty file is: /home/river/git_new/linux-stable/net/core/rtnetlink.c. == [ INFO

kernel 3.18.57 :WARNING in dev_watchdog

Hi: I've got the following error report while fuzzing the kernel with syzkaller on linux-3.18.57. I'd submitted a similar bug On June 15th: https://mail.google.com/mail/#inbox/15c9ae21d9300405?compose=15cc9df0658a7669 But this time i got some reproducer in linux-3.18.57(no kov) -

Re: kernel BUG at net/ipv4/tcp_output.c:2748!

Hi: I tested the PoC on v3.18 ~ v4.11,all the kenel have crashed.But,The v4.12-rc4 version is not affected thanks. 2017-06-13 21:02 GMT+08:00 Greg KH : > On Tue, Jun 13, 2017 at 07:39:00PM +0800, Dison River wrote: >> Hi >>I've got the following error report while fuz

kernel BUG at net/ipv4/tcp_output.c:2748!

Hi I've got the following error report while fuzzing the kernel on linux-4.11.0-rc3.

Re: WARNING in dev_watchdog

Sorry,this WARNING is not reproducible.And I don't have PoC for this bug. 2017-06-12 14:42 GMT+08:00 Greg KH : > On Mon, Jun 12, 2017 at 02:37:22PM +0800, Dison River wrote: >> Hi: >> I've got the following error report while fuzzing the kernel with >> syzkaller

WARNING in dev_watchdog

Hi: I've got the following error report while fuzzing the kernel with syzkaller on linux-4.11.0-rc3. log: WARNING: CPU: 2 PID: 0 at net/sched/sch_generic.c:316 dev_watchdog+0x648/0x770 net/sched/sch_generic.c:315 NETDEV WATCHDOG: eth0 (e1000): transmit queue 0 timed out Kernel panic - not sync