All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+34ad5fab48f7bf510349@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [syzbot] [PATCH net] netlink: Fix kernel-infoleak in __skb_datagram_iter()
Date: Tue, 20 Feb 2024 04:00:39 -0800	[thread overview]
Message-ID: <0000000000007edeaa0611cef5cc@google.com> (raw)
In-Reply-To: <0000000000002cf4690610660f71@google.com>

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.

***

Subject: [PATCH net] netlink: Fix kernel-infoleak in __skb_datagram_iter()
Author: ryasuoka@redhat.com

#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 5bd7ef53ffe5ca580e93e74eb8c81ed191ddc4bd

diff --git a/net/netlink/af_netlink.c b/net/netlink/af_netlink.c
index eb086b06d60d..8277399d19b3 100644
--- a/net/netlink/af_netlink.c
+++ b/net/netlink/af_netlink.c
@@ -167,7 +167,7 @@ static inline u32 netlink_group_mask(u32 group)
 static struct sk_buff *netlink_to_full_skb(const struct sk_buff *skb,
                                           gfp_t gfp_mask)
 {
-       unsigned int len = skb_end_offset(skb);
+       unsigned int len = skb->len;
        struct sk_buff *new;

        new = alloc_skb(len, gfp_mask);


      parent reply	other threads:[~2024-02-20 12:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-02 13:26 [syzbot] [net?] KMSAN: kernel-infoleak in __skb_datagram_iter (2) syzbot
2024-02-15  9:27 ` [syzbot] [PATCH] net: Fix " syzbot
2024-02-17 12:40 ` [syzbot] " syzbot
2024-02-17 14:51 ` syzbot
2024-02-20  2:42 ` [syzbot] [PATCH net] netlink: Fix kernel-infoleak in __skb_datagram_iter() syzbot
2024-02-20  4:49 ` syzbot
2024-02-20  7:16 ` [syzbot] Test for 34ad5fab48f7bf510349 syzbot
2024-02-20 12:00 ` syzbot [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=0000000000007edeaa0611cef5cc@google.com \
    --to=syzbot+34ad5fab48f7bf510349@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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.