From: Lee Jones <lee@kernel•org>
To: Zheng Hacker <hackerzheng666@gmail•com>
Cc: Sergey Shtylyov <s.shtylyov@omp•ru>,
Jakub Kicinski <kuba@kernel•org>, Zheng Wang <zyytlz.wz@163•com>,
davem@davemloft•net, linyunsheng@huawei•com, edumazet@google•com,
pabeni@redhat•com, netdev@vger•kernel.org,
linux-kernel@vger•kernel.org, 1395428693sheep@gmail•com,
alex000young@gmail•com
Subject: Re: [PATCH net v3] net: ravb: Fix possible UAF bug in ravb_remove
Date: Mon, 17 Jul 2023 14:04:08 +0100 [thread overview]
Message-ID: <20230717130408.GC1082701@google.com> (raw)
In-Reply-To: <CAJedcCydqmVBrNq_RCDF2gRds39XqWORFi32MV+9LGa5p28dPQ@mail.gmail.com>
On Sun, 16 Jul 2023, Zheng Hacker wrote:
> Zheng Hacker <hackerzheng666@gmail•com> 于2023年7月16日周日 10:11写道：
> >
> > Hello,
> >
> > This bug is found by static analysis. I'm sorry that my friends apply
> > for a CVE number before we really fix it. We made a list about the
> > bugs we have submitted and wouldn't disclose them before the fix. But
> > we had a inconsistent situation last month. And we applied it by
> > mistake foe we thought we had fixed it. And so sorry about my late
> > reply, I'll see the patch right now.
> >
> > Best regards,
> > Zheng Wang
> >
> > Sergey Shtylyov <s.shtylyov@omp•ru> 于2023年7月16日周日 04:48写道：
> > >
> > > On 7/15/23 7:07 PM, Zheng Hacker wrote:
> > >
> > > > Sorry for my late reply. I'll see what I can do later.
> > >
> > > That's good to hear!
> > > Because I'm now only able to look at it during weekends...
> > >
> > > > Lee Jones <lee@kernel•org> 于2023年7月12日周三 19:56写道：
> > > >>
> > > >> On Mon, 10 Jul 2023, Jakub Kicinski wrote:
> > > >>
> > > >>> On Mon, 10 Jul 2023 12:42:53 +0100 Lee Jones wrote:
> > > >>>> For better or worse, it looks like this issue was assigned a CVE.
> > > >>>
> > > >>> Ugh, what a joke.
> > > >>
> > > >> I think that's putting it politely. :)
>
> After reviewing the code, I think it's better to put the code in
> ravb_remove. For the ravb_remove is bound with the device and
> ravb_close is bound with the file. We may not call ravb_close if
> there's no file opened.
When you do submit this, would you be kind enough to Cc me please?
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2023-07-17 13:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-11 18:06 [PATCH net v3] net: ravb: Fix possible UAF bug in ravb_remove Zheng Wang
2023-03-12 20:26 ` Sergey Shtylyov
2023-03-13 3:00 ` Zheng Hacker
2023-03-13 1:15 ` Yunsheng Lin
2023-03-13 3:02 ` Zheng Hacker
2023-03-13 3:32 ` Yunsheng Lin
2023-03-13 9:34 ` Zheng Hacker
2023-07-19 21:04 ` Sergey Shtylyov
2023-03-13 22:39 ` Jakub Kicinski
2023-03-14 1:24 ` Zheng Hacker
2023-07-05 8:05 ` Lee Jones
2023-07-10 11:42 ` Lee Jones
2023-07-10 16:15 ` Jakub Kicinski
2023-07-11 21:20 ` Sergey Shtylyov
2023-07-12 11:56 ` Lee Jones
2023-07-15 16:07 ` Zheng Hacker
2023-07-15 20:48 ` Sergey Shtylyov
2023-07-16 2:11 ` Zheng Hacker
2023-07-16 3:14 ` Zheng Hacker
2023-07-17 13:04 ` Lee Jones [this message]
2023-07-17 13:21 ` Zheng Hacker
2023-07-24 9:20 ` Lee Jones
2023-07-25 2:26 ` Zheng Hacker
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=20230717130408.GC1082701@google.com \
--to=lee@kernel$(echo .)org \
--cc=1395428693sheep@gmail$(echo .)com \
--cc=alex000young@gmail$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=hackerzheng666@gmail$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linyunsheng@huawei$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=s.shtylyov@omp$(echo .)ru \
--cc=zyytlz.wz@163$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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