From: Jakub Kicinski <kuba@kernel.org>
To: Shigeru Yoshida <syoshida@redhat.com>
Cc: davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
syzbot+b563d33852b893653a9e@syzkaller.appspotmail.com
Subject: Re: [PATCH net] net: caif: Fix use-after-free in cfusbl_device_notify()
Date: Mon, 27 Feb 2023 18:28:00 -0800 [thread overview]
Message-ID: <20230227182800.02ddf83f@kernel.org> (raw)
In-Reply-To: <20230225182820.4048336-1-syoshida@redhat.com>
On Sun, 26 Feb 2023 03:28:20 +0900 Shigeru Yoshida wrote:
> syzbot reported use-after-free in cfusbl_device_notify() [1]. This
> causes a stack trace like below:
Please repost with the correct fixes tag, presumably:
Fixes: 7ad65bf68d70 ("caif: Add support for CAIF over CDC NCM USB interface")
Please make sure you CC the authors of that commit.
next prev parent reply other threads:[~2023-02-28 2:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-25 18:28 [PATCH net] net: caif: Fix use-after-free in cfusbl_device_notify() Shigeru Yoshida
2023-02-28 2:28 ` Jakub Kicinski [this message]
2023-02-28 16:52 ` Shigeru Yoshida
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=20230227182800.02ddf83f@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syoshida@redhat.com \
--cc=syzbot+b563d33852b893653a9e@syzkaller.appspotmail.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).