From: Santosh Shilimkar <santosh.shilimkar@oracle.com>
To: Eric Biggers <ebiggers3@gmail.com>
Cc: syzkaller-bugs@googlegroups.com,
Avinash Repaka <avinash.repaka@oracle.com>,
syzbot
<bot+9461c9b9d340854a404b46c42cbfc91ded1232d8@syzkaller.appspotmail.com>,
davem@davemloft.net, linux-kernel@vger.kernel.org,
linux-rdma@vger.kernel.org, netdev@vger.kernel.org,
rds-devel@oss.oracle.com
Subject: Re: KASAN: stack-out-of-bounds Read in rds_sendmsg
Date: Tue, 30 Jan 2018 18:55:32 -0800 [thread overview]
Message-ID: <5db55967-3608-d9cc-768a-e75dc61ed311@oracle.com> (raw)
In-Reply-To: <20180131021638.6h5fukvzzakzu5g2@gmail.com>
On 1/30/2018 6:16 PM, Eric Biggers wrote:
> On Thu, Dec 21, 2017 at 08:44:32AM -0800, Santosh Shilimkar wrote:
>> +Avinash
>>
>> On 12/21/2017 1:10 AM, syzbot wrote:
>>> syzkaller has found reproducer for the following crash on
>>
>> [..]
>>
>>>
>>> audit: type=1400 audit(1513847224.110:7): avc: denied { map } for
>>> pid=3157 comm="syzkaller455006" path="/root/syzkaller455006870"
>>> dev="sda1" ino=16481
>>> scontext=unconfined_u:system_r:insmod_t:s0-s0:c0.c1023
>>> tcontext=unconfined_u:object_r:user_home_t:s0 tclass=file permissive=1
>>> ==================================================================
>>> BUG: KASAN: stack-out-of-bounds in rds_rdma_bytes net/rds/send.c:1013
>>> [inline]
>>
>> Could you please post the discussed fix if you are ready with it ?
>> This new report is same as last one and cmesg length check should
>> address it.
>>
[...]
>
> This crash seems to have stopped occurring. I assume it was fixed by commit
> 14e138a86f63 (thanks Avinash!), so let's tell syzbot so that it can start
> reporting crashes in the same place again:
>
> #syz fix: RDS: Check cmsg_len before dereferencing CMSG_DATA
>
Thanks Eric for confirmation !!
Regards,
Santosh
prev parent reply other threads:[~2018-01-31 2:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-09 10:41 KASAN: stack-out-of-bounds Read in rds_sendmsg syzbot
2017-12-21 9:10 ` syzbot
2017-12-21 16:44 ` Santosh Shilimkar
2018-01-31 2:16 ` Eric Biggers
2018-01-31 2:55 ` Santosh Shilimkar [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5db55967-3608-d9cc-768a-e75dc61ed311@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=avinash.repaka@oracle.com \
--cc=bot+9461c9b9d340854a404b46c42cbfc91ded1232d8@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=ebiggers3@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rds-devel@oss.oracle.com \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).