From: patchwork-bot+netdevbpf@kernel.org
To: Ziyang Xuan <william.xuanziyang@huawei.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, ap420073@gmail.com
Subject: Re: [PATCH net v2] macsec: fix UAF bug for real_dev
Date: Wed, 01 Jun 2022 10:50:12 +0000 [thread overview]
Message-ID: <165408061228.2193.2356708957505093966.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220531074500.1272846-1-william.xuanziyang@huawei.com>
Hello:
This patch was applied to netdev/net.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 31 May 2022 15:45:00 +0800 you wrote:
> Create a new macsec device but not get reference to real_dev. That can
> not ensure that real_dev is freed after macsec. That will trigger the
> UAF bug for real_dev as following:
>
> ==================================================================
> BUG: KASAN: use-after-free in macsec_get_iflink+0x5f/0x70 drivers/net/macsec.c:3662
> Call Trace:
> ...
> macsec_get_iflink+0x5f/0x70 drivers/net/macsec.c:3662
> dev_get_iflink+0x73/0xe0 net/core/dev.c:637
> default_operstate net/core/link_watch.c:42 [inline]
> rfc2863_policy+0x233/0x2d0 net/core/link_watch.c:54
> linkwatch_do_dev+0x2a/0x150 net/core/link_watch.c:161
>
> [...]
Here is the summary with links:
- [net,v2] macsec: fix UAF bug for real_dev
https://git.kernel.org/netdev/net/c/196a888ca657
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-06-01 10:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 7:45 [PATCH net v2] macsec: fix UAF bug for real_dev Ziyang Xuan
2022-06-01 10:50 ` patchwork-bot+netdevbpf [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=165408061228.2193.2356708957505093966.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ap420073@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=william.xuanziyang@huawei.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).