[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJsXRPEZV=ugCAxngtVRt+=GZfnwf1abxu8Q_DSaPeXuTYpsVw@mail.gmail.com>
Date: Tue, 4 Jul 2017 13:12:18 +0800
From: Dison River <pwn2river@...il.com>
To: samuel@...tiz.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, qca_merez@....qualcomm.com,
kvalo@...eaurora.org, linux-wireless@...r.kernel.org,
jakub.kicinski@...ronome.com, davem@...emloft.net,
oss-drivers@...ronome.com, security@...nel.org,
wil6210@....qualcomm.com
Subject: '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.12-rc7
drivers/net/irda/vlsi_ir.c:326 seq_printf(seq, "skb=%p
data=%p hw=%p\n", rd->skb, rd->buf, rd->hw);
drivers/net/ethernet/netronome/nfp/nfp_net_debugfs.c:167
seq_printf(file, " frag=%p", skb);
drivers/net/wireless/ath/wil6210/debugfs.c:926 seq_printf(s,
" SKB = 0x%p\n", skb);
Thanks.
Powered by blists - more mailing lists