From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id A4CE7C433F5 for ; Mon, 14 Feb 2022 18:47:03 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231625AbiBNSrJ (ORCPT ); Mon, 14 Feb 2022 13:47:09 -0500 Received: from gmail-smtp-in.l.google.com ([23.128.96.19]:46888 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229821AbiBNSrD (ORCPT ); Mon, 14 Feb 2022 13:47:03 -0500 Received: from mail-io1-f70.google.com (mail-io1-f70.google.com [209.85.166.70]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B958C70913 for ; Mon, 14 Feb 2022 10:46:47 -0800 (PST) Received: by mail-io1-f70.google.com with SMTP id y124-20020a6bc882000000b0060fbfe14d03so11158629iof.2 for ; Mon, 14 Feb 2022 10:46:47 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=qMoLJBAbF6b15k+JxV0FF5gwlXjQrey2dRuI3+dpzKE=; b=4n666PaJKZ+TQRR7K0dL/VfmDAlLIrZ+DtpkvQoFXj206VabJxGp0t7lRu5Rbr6DV/ /KnsiZ6Ww3oZDes2aKZ6l83wC3k2m7gt69r+qLq2sTwhu59/W6GDjr+g1f8Fa/dawF2u 9JXAf/HgkvzH2tmR8opDLqQfNYgiYnQ/jqEHcZbj5j5gO1ATgLqgUHZjcyHAdccVSXNe NHbMjdsq8LqbfQNyoGxSUYMYCVNptOz7P2IKO9GRhveBY9gV6OZCOwzdosavqk8acTBV bL12sabWLRgILjUnOz4j0AcL7XJnhj1xRAE33H2EdikwldeITiIVLnOn+getNsac1JwA uE2Q== X-Gm-Message-State: AOAM531r3gVvFuQWYJUxTbK6MEnV8Yk+TTvTeRcFTCbCfQ2myryM+6F0 oQWXtEdyhO6vyxBDB24yP7V2PJdzCDCwDHyWrj/plg2Zx9SX X-Google-Smtp-Source: ABdhPJwr8DWPrO5HIF0EfWDSQp/4Hswh9YS6I9drsyxbeZ4K29bwe92mTlOZljIfSHNojoENzUFgRY+/bLTcDqG9Ym4p46X8WNmx MIME-Version: 1.0 X-Received: by 2002:a05:6e02:1586:: with SMTP id m6mr120117ilu.233.1644864319237; Mon, 14 Feb 2022 10:45:19 -0800 (PST) Date: Mon, 14 Feb 2022 10:45:19 -0800 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <00000000000073b3e805d7fed17e@google.com> Subject: [syzbot] KASAN: vmalloc-out-of-bounds Read in bpf_jit_free From: syzbot To: andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org, daniel@iogearbox.net, davem@davemloft.net, hawk@kernel.org, john.fastabend@gmail.com, kafai@fb.com, kpsingh@kernel.org, kuba@kernel.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, songliubraving@fb.com, syzkaller-bugs@googlegroups.com, yhs@fb.com Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, syzbot found the following issue on: HEAD commit: e5313968c41b Merge branch 'Split bpf_sk_lookup remote_port.. git tree: bpf-next console output: https://syzkaller.appspot.com/x/log.txt?x=10baced8700000 kernel config: https://syzkaller.appspot.com/x/.config?x=c40b67275bfe2a58 dashboard link: https://syzkaller.appspot.com/bug?extid=2f649ec6d2eea1495a8f compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 Unfortunately, I don't have any reproducer for this issue yet. IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+2f649ec6d2eea1495a8f@syzkaller.appspotmail.com ================================================================== BUG: KASAN: vmalloc-out-of-bounds in bpf_jit_binary_pack_free kernel/bpf/core.c:1120 [inline] BUG: KASAN: vmalloc-out-of-bounds in bpf_jit_free+0x2b5/0x2e0 kernel/bpf/core.c:1151 Read of size 4 at addr ffffffffa0001a80 by task kworker/0:18/13642 CPU: 0 PID: 13642 Comm: kworker/0:18 Not tainted 5.16.0-syzkaller-11655-ge5313968c41b #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Workqueue: events bpf_prog_free_deferred Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106 print_address_description.constprop.0.cold+0xf/0x336 mm/kasan/report.c:255 __kasan_report mm/kasan/report.c:442 [inline] kasan_report.cold+0x83/0xdf mm/kasan/report.c:459 bpf_jit_binary_pack_free kernel/bpf/core.c:1120 [inline] bpf_jit_free+0x2b5/0x2e0 kernel/bpf/core.c:1151 bpf_prog_free_deferred+0x5c1/0x790 kernel/bpf/core.c:2524 process_one_work+0x9ac/0x1650 kernel/workqueue.c:2307 worker_thread+0x657/0x1110 kernel/workqueue.c:2454 kthread+0x2e9/0x3a0 kernel/kthread.c:377 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295 Memory state around the buggy address: ffffffffa0001980: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 ffffffffa0001a00: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 >ffffffffa0001a80: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 ^ ffffffffa0001b00: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 ffffffffa0001b80: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 ================================================================== --- This report is generated by a bot. It may contain errors. See https://goo.gl/tpsmEJ for more information about syzbot. syzbot engineers can be reached at syzkaller@googlegroups.com. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot.