From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+bfde3bef047a81b8fde6@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] KASAN: use-after-free Read in __skb_flow_dissect (3)
Date: Thu, 18 Jan 2024 20:08:12 +0800 [thread overview]
Message-ID: <20240118120812.1575-1-hdanton@sina.com> (raw)
In-Reply-To: <000000000000498a02060de59162@google.com>
On Mon, 01 Jan 2024 09:18:16 -0800
> syzbot found the following issue on:
>
> HEAD commit: f5837722ffec Merge tag 'mm-hotfixes-stable-2023-12-27-15-0..
> git tree: upstream
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=122dfc65e80000
#syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
--- x/net/core/filter.c
+++ y/net/core/filter.c
@@ -2144,6 +2144,7 @@ static int __bpf_redirect_no_mac(struct
unsigned int mlen = skb_network_offset(skb);
if (unlikely(skb->len <= mlen)) {
+out:
kfree_skb(skb);
return -ERANGE;
}
@@ -2159,6 +2160,8 @@ static int __bpf_redirect_no_mac(struct
if (!skb_at_tc_ingress(skb))
skb_postpull_rcsum(skb, skb_mac_header(skb), mlen);
}
+ if (skb->len <= sizeof(struct iphdr))
+ goto out;
skb_pop_mac_header(skb);
skb_reset_mac_len(skb);
return flags & BPF_F_INGRESS ?
@@ -2431,7 +2434,7 @@ enum {
BPF_CALL_3(bpf_clone_redirect, struct sk_buff *, skb, u32, ifindex, u64, flags)
{
struct net_device *dev;
- struct sk_buff *clone;
+ struct sk_buff *buf;
int ret;
if (unlikely(flags & (~(BPF_F_INGRESS) | BPF_F_REDIRECT_INTERNAL)))
@@ -2441,22 +2444,11 @@ BPF_CALL_3(bpf_clone_redirect, struct sk
if (unlikely(!dev))
return -EINVAL;
- clone = skb_clone(skb, GFP_ATOMIC);
- if (unlikely(!clone))
+ buf = skb_copy(skb, GFP_ATOMIC);
+ if (unlikely(!buf))
return -ENOMEM;
- /* For direct write, we need to keep the invariant that the skbs
- * we're dealing with need to be uncloned. Should uncloning fail
- * here, we need to free the just generated clone to unclone once
- * again.
- */
- ret = bpf_try_make_head_writable(skb);
- if (unlikely(ret)) {
- kfree_skb(clone);
- return -ENOMEM;
- }
-
- return __bpf_redirect(clone, dev, flags);
+ return __bpf_redirect(buf, dev, flags);
}
static const struct bpf_func_proto bpf_clone_redirect_proto = {
--
next prev parent reply other threads:[~2024-01-18 12:09 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-01 17:18 syzbot
2024-01-17 11:23 ` Hillf Danton
2024-01-17 11:58 ` syzbot
2024-01-17 13:14 ` Hillf Danton
2024-01-17 13:35 ` syzbot
2024-01-17 22:51 ` Hillf Danton
2024-01-17 23:16 ` syzbot
2024-01-17 23:43 ` Hillf Danton
2024-01-18 0:18 ` syzbot
2024-01-18 2:33 ` Hillf Danton
2024-01-18 2:55 ` syzbot
2024-01-18 4:33 ` Hillf Danton
2024-01-18 4:47 ` syzbot
2024-01-18 11:17 ` Hillf Danton
2024-01-18 11:47 ` syzbot
2024-01-18 12:08 ` Hillf Danton [this message]
2024-01-18 12:31 ` syzbot
2024-01-18 13:17 ` Hillf Danton
2024-01-18 13:40 ` syzbot
2024-01-18 22:15 ` Hillf Danton
2024-01-18 22:34 ` syzbot
2024-01-19 4:49 ` Hillf Danton
2024-01-19 5:22 ` syzbot
2024-01-19 7:38 ` Hillf Danton
2024-01-19 8:01 ` syzbot
2024-01-19 10:31 ` Hillf Danton
2024-01-19 10:47 ` syzbot
2024-01-19 11:47 ` Hillf Danton
2024-01-19 12:07 ` syzbot
2024-02-20 13:05 ` [syzbot] KASAN: use-after-free Read in __skb_flow_dissect syzbot
[not found] <20240220130510.GC19387@breakpoint.cc>
2024-02-20 13:27 ` [syzbot] [net?] KASAN: use-after-free Read in __skb_flow_dissect (3) 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=20240118120812.1575-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+bfde3bef047a81b8fde6@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®