From: syzbot <syzbot+431f9a9e3f5227fbb904@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Forwarded: [PATCH] udp_bpf: fix use-after-free in udp_bpf_recvmsg()
Date: Wed, 01 Apr 2026 19:16:51 -0700 [thread overview]
Message-ID: <69cdd193.050a0220.25c253.047a.GAE@google.com> (raw)
In-Reply-To: <69cdbd12.050a0220.70c3a.0007.GAE@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: [PATCH] udp_bpf: fix use-after-free in udp_bpf_recvmsg()
Author: kartikey406@gmail.com
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git main
udp_bpf_recvmsg() calls sk_msg_recvmsg() without holding lock_sock(),
unlike tcp_bpf_recvmsg() which properly acquires lock_sock() before
calling __sk_msg_recvmsg(). This allows concurrent tasks to race inside
sk_msg_recvmsg() on the same psock ingress queue, where one task can
free msg_rx via kfree_sk_msg() while another task is still reading it
via sk_msg_elem(), causing a slab-use-after-free.
Fix this by adding lock_sock()/release_sock() pairs around the recvmsg
path. Since udp_msg_wait_data() does not release lock_sock() internally
before sleeping (unlike tcp_msg_wait_data()), we must release the socket
lock manually before calling udp_msg_wait_data() and reacquire it after
to avoid a deadlock with the ingress path delivering new data.
Reported-by: syzbot+431f9a9e3f5227fbb904@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=431f9a9e3f5227fbb904
Fixes: 1f5be6b3b063 ("udp: Implement udp_bpf_recvmsg() for sockmap")
Signed-off-by: Deepanshu Kartikey <kartikey406@gmail.com>
---
net/ipv4/udp_bpf.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/net/ipv4/udp_bpf.c b/net/ipv4/udp_bpf.c
index 9f33b07b1481..5e6d82816103 100644
--- a/net/ipv4/udp_bpf.c
+++ b/net/ipv4/udp_bpf.c
@@ -74,7 +74,9 @@ static int udp_bpf_recvmsg(struct sock *sk, struct msghdr *msg, size_t len,
if (unlikely(!psock))
return sk_udp_recvmsg(sk, msg, len, flags);
+ lock_sock(sk);
if (!psock_has_data(psock)) {
+ release_sock(sk);
ret = sk_udp_recvmsg(sk, msg, len, flags);
goto out;
}
@@ -86,16 +88,20 @@ static int udp_bpf_recvmsg(struct sock *sk, struct msghdr *msg, size_t len,
int data;
timeo = sock_rcvtimeo(sk, flags & MSG_DONTWAIT);
+ release_sock(sk);
data = udp_msg_wait_data(sk, psock, timeo);
+ lock_sock(sk);
if (data) {
if (psock_has_data(psock))
goto msg_bytes_ready;
+ release_sock(sk);
ret = sk_udp_recvmsg(sk, msg, len, flags);
goto out;
}
copied = -EAGAIN;
}
ret = copied;
+ release_sock(sk);
out:
sk_psock_put(sk, psock);
return ret;
--
2.43.0
next prev parent reply other threads:[~2026-04-02 2:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 0:49 [syzbot] [net?] [bpf?] KASAN: slab-use-after-free Read in __sk_msg_recvmsg syzbot
2026-04-02 2:16 ` syzbot [this message]
2026-04-02 4:28 ` Forwarded: [PATCH] udp_bpf: fix use-after-free in udp_bpf_recvmsg() syzbot
2026-05-21 15:23 ` Forwarded: #syz test https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net-next 73366893d1d58d247bef70406280f71030495424 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=69cdd193.050a0220.25c253.047a.GAE@google.com \
--to=syzbot+431f9a9e3f5227fbb904@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.