All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Lee Jones <lee@kernel.org>, s.shtylyov@omp.ru
Cc: 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, hackerzheng666@gmail.com,
	1395428693sheep@gmail.com, alex000young@gmail.com
Subject: Re: [PATCH net v3] net: ravb: Fix possible UAF bug in ravb_remove
Date: Mon, 10 Jul 2023 09:15:45 -0700	[thread overview]
Message-ID: <20230710091545.5df553fc@kernel.org> (raw)
In-Reply-To: <20230710114253.GA132195@google.com>

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. 

Sergey, could you take a look at fixing this properly?

  reply	other threads:[~2023-07-10 16:15 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 [this message]
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
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=20230710091545.5df553fc@kernel.org \
    --to=kuba@kernel.org \
    --cc=1395428693sheep@gmail.com \
    --cc=alex000young@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hackerzheng666@gmail.com \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linyunsheng@huawei.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=s.shtylyov@omp.ru \
    --cc=zyytlz.wz@163.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.