From: patchwork-bot+netdevbpf@kernel.org
To: Ryosuke Yasuoka <ryasuoka@redhat.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org,
anjali.k.kulkarni@oracle.com, lirongqing@baidu.com,
dhowells@redhat.com, pctammela@mojatatu.com, kuniyu@amazon.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
syzbot+34ad5fab48f7bf510349@syzkaller.appspotmail.com
Subject: Re: [PATCH net] netlink: Fix kernel-infoleak-after-free in __skb_datagram_iter
Date: Fri, 23 Feb 2024 03:10:26 +0000 [thread overview]
Message-ID: <170865782631.16544.1371911549002746191.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240221074053.1794118-1-ryasuoka@redhat.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 21 Feb 2024 16:40:48 +0900 you wrote:
> syzbot reported the following uninit-value access issue [1]:
>
> netlink_to_full_skb() creates a new `skb` and puts the `skb->data`
> passed as a 1st arg of netlink_to_full_skb() onto new `skb`. The data
> size is specified as `len` and passed to skb_put_data(). This `len`
> is based on `skb->end` that is not data offset but buffer offset. The
> `skb->end` contains data and tailroom. Since the tailroom is not
> initialized when the new `skb` created, KMSAN detects uninitialized
> memory area when copying the data.
>
> [...]
Here is the summary with links:
- [net] netlink: Fix kernel-infoleak-after-free in __skb_datagram_iter
https://git.kernel.org/netdev/net/c/661779e1fcaf
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:[~2024-02-23 3:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 7:40 [PATCH net] netlink: Fix kernel-infoleak-after-free in __skb_datagram_iter Ryosuke Yasuoka
2024-02-21 7:55 ` Eric Dumazet
2024-02-23 3:10 ` 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=170865782631.16544.1371911549002746191.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=anjali.k.kulkarni@oracle.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lirongqing@baidu.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pctammela@mojatatu.com \
--cc=ryasuoka@redhat.com \
--cc=syzbot+34ad5fab48f7bf510349@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