From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+9307c991a6d07ce6e6d8@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bpf?] [net?] KASAN: slab-use-after-free Read in sk_msg_recvmsg
Date: Mon, 16 Feb 2026 13:16:00 +0800 [thread overview]
Message-ID: <20260216051603.3161-1-hdanton@sina.com> (raw)
In-Reply-To: <69922ac9.a70a0220.2c38d7.00e0.GAE@google.com>
> Date: Sun, 15 Feb 2026 12:21:29 -0800 [thread overview]
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: a040afa3bca4 gve: fix probe failure if clock read fails
> git tree: net
> console output: https://syzkaller.appspot.com/x/log.txt?x=165bf05a580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=e3161cabe5a361ff
> dashboard link: https://syzkaller.appspot.com/bug?extid=9307c991a6d07ce6e6d8
> compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13dd245a580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16ecdb2a580000
#syz test
--- x/net/core/skmsg.c
+++ y/net/core/skmsg.c
@@ -500,7 +500,13 @@ out:
int sk_msg_recvmsg(struct sock *sk, struct sk_psock *psock, struct msghdr *msg,
int len, int flags)
{
- return __sk_msg_recvmsg(sk, psock, msg, len, flags, NULL);
+ static DEFINE_MUTEX(lk);
+ int rc;
+
+ mutex_lock(&lk);
+ rc = __sk_msg_recvmsg(sk, psock, msg, len, flags, NULL);
+ mutex_unlock(&lk);
+ return rc;
}
EXPORT_SYMBOL_GPL(sk_msg_recvmsg);
--
next prev parent reply other threads:[~2026-02-16 5:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-15 20:21 syzbot
2026-02-16 0:59 ` Hillf Danton
2026-02-16 2:10 ` syzbot
2026-02-16 5:16 ` Hillf Danton [this message]
2026-02-16 5:36 ` syzbot
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=20260216051603.3161-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+9307c991a6d07ce6e6d8@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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
all inboxes | Powered by JetHome®