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 ED69EE7109A for ; Thu, 21 Sep 2023 16:57:59 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229594AbjIUQ6D (ORCPT ); Thu, 21 Sep 2023 12:58:03 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54074 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229639AbjIUQ6A (ORCPT ); Thu, 21 Sep 2023 12:58:00 -0400 Received: from mail-oo1-f79.google.com (mail-oo1-f79.google.com [209.85.161.79]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 76FE3E5A for ; Thu, 21 Sep 2023 09:56:42 -0700 (PDT) Received: by mail-oo1-f79.google.com with SMTP id 006d021491bc7-57b2fa97912so1566030eaf.1 for ; Thu, 21 Sep 2023 09:56:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695315401; x=1695920201; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=Ww3vN035Zcg12MFBbqgS3GHytBFID7A4JA0YJ0J/nwk=; b=vrdhZCCqKCkhf9Tr77dM/VsBLphIGrs1FCxjTtASUaiXyg33WgvvhjRU0ARZoE4h7m 4hOkgxnkjlrPnkntExqLAqgE0gRf6J7sRmV3j92Cz7vmsK7zPDpHuyP2B34toyQlvVdp msF2cHcdtnKXP4c7lgGomL38nxuheiMZKk0yC7moe+vDxY2ra3n0QO1bk05eGb6HKVsX 5LtX4/596wpv8/upfM+a+cvLv3WERFNRPGGA2iwW5Wv/iunO4Tz50HjKpqDoN3g5FeMF UOzjoqOklDs5W0LRJYssoIf/+DupJwj3dcPwmdeVaE0segHtoxLU0aZU1AMo28QfBNY0 YkwA== X-Gm-Message-State: AOJu0Yy5ZcBj0pglmXzcXd5PybIPcrpOGa9YPVXaeOl8lS63rC93oCAy Re1TWMwIoDXdD7TDt26u6rLzoTdQwyr1qnazVL+Kx7vpXrfV X-Google-Smtp-Source: AGHT+IHbTeYpEXb5ZcMqasZzdDOda0xsCGxKjaQXWGJjZ5l/1+vN/CmuAzvLqhtikQr2cdXj4pwFkJaFHV3OkwSbBwgcSAx9pITO MIME-Version: 1.0 X-Received: by 2002:a05:6870:1a98:b0:1d6:4b44:a3d0 with SMTP id ef24-20020a0568701a9800b001d64b44a3d0mr2508372oab.6.1695315401731; Thu, 21 Sep 2023 09:56:41 -0700 (PDT) Date: Thu, 21 Sep 2023 09:56:41 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <0000000000004d83170605e16003@google.com> Subject: [syzbot] [net?] memory leak in tcp_md5_do_add From: syzbot To: bpf@vger.kernel.org, davem@davemloft.net, dsahern@kernel.org, edumazet@google.com, kuba@kernel.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, pabeni@redhat.com, syzkaller-bugs@googlegroups.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: ee3f96b16468 Merge tag 'nfsd-6.3-1' of git://git.kernel.or.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=1312bba8c80000 kernel config: https://syzkaller.appspot.com/x/.config?x=f5733ca1757172ad dashboard link: https://syzkaller.appspot.com/bug?extid=68662811b3d5f6695bcb compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=105393a8c80000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1113917f480000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/29e7966ab711/disk-ee3f96b1.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/ae21b8e855de/vmlinux-ee3f96b1.xz kernel image: https://storage.googleapis.com/syzbot-assets/803ee0425ad6/bzImage-ee3f96b1.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+68662811b3d5f6695bcb@syzkaller.appspotmail.com executing program BUG: memory leak unreferenced object 0xffff88810a86f7a0 (size 32): comm "syz-executor325", pid 5099, jiffies 4294978342 (age 119.240s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [] kmalloc_trace+0x24/0x90 mm/slab_common.c:1061 [] kmalloc include/linux/slab.h:580 [inline] [] tcp_md5sig_info_add net/ipv4/tcp_ipv4.c:1169 [inline] [] tcp_md5_do_add+0xa0/0x150 net/ipv4/tcp_ipv4.c:1240 [] tcp_v6_parse_md5_keys+0x253/0x4a0 net/ipv6/tcp_ipv6.c:671 [] do_tcp_setsockopt+0x40e/0x1360 net/ipv4/tcp.c:3720 [] tcp_setsockopt+0x9b/0xa0 net/ipv4/tcp.c:3806 [] __sys_setsockopt+0x1ab/0x330 net/socket.c:2274 [] __do_sys_setsockopt net/socket.c:2285 [inline] [] __se_sys_setsockopt net/socket.c:2282 [inline] [] __x64_sys_setsockopt+0x26/0x30 net/socket.c:2282 [] do_syscall_x64 arch/x86/entry/common.c:50 [inline] [] do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80 [] entry_SYSCALL_64_after_hwframe+0x63/0xcd BUG: memory leak unreferenced object 0xffff88811225ccc0 (size 192): comm "syz-executor325", pid 5099, jiffies 4294978342 (age 119.240s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 22 01 00 00 00 00 ad de ........"....... 22 0a 80 00 fe 80 00 00 00 00 00 00 00 00 00 00 "............... backtrace: [] __do_kmalloc_node mm/slab_common.c:966 [inline] [] __kmalloc+0x4a/0x120 mm/slab_common.c:980 [] kmalloc include/linux/slab.h:584 [inline] [] sock_kmalloc net/core/sock.c:2635 [inline] [] sock_kmalloc+0x65/0xa0 net/core/sock.c:2624 [] __tcp_md5_do_add+0xcb/0x300 net/ipv4/tcp_ipv4.c:1212 [] tcp_md5_do_add+0x67/0x150 net/ipv4/tcp_ipv4.c:1253 [] tcp_v6_parse_md5_keys+0x253/0x4a0 net/ipv6/tcp_ipv6.c:671 [] do_tcp_setsockopt+0x40e/0x1360 net/ipv4/tcp.c:3720 [] tcp_setsockopt+0x9b/0xa0 net/ipv4/tcp.c:3806 [] __sys_setsockopt+0x1ab/0x330 net/socket.c:2274 [] __do_sys_setsockopt net/socket.c:2285 [inline] [] __se_sys_setsockopt net/socket.c:2282 [inline] [] __x64_sys_setsockopt+0x26/0x30 net/socket.c:2282 [] do_syscall_x64 arch/x86/entry/common.c:50 [inline] [] do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80 [] entry_SYSCALL_64_after_hwframe+0x63/0xcd --- 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. If the bug is already fixed, let syzbot know by replying with: #syz fix: exact-commit-title If you want syzbot to run the reproducer, reply with: #syz test: git://repo/address.git branch-or-commit-hash If you attach or paste a git patch, syzbot will apply it before testing. If you want to overwrite bug's subsystems, reply with: #syz set subsystems: new-subsystem (See the list of subsystem names on the web dashboard) If the bug is a duplicate of another bug, reply with: #syz dup: exact-subject-of-another-report If you want to undo deduplication, reply with: #syz undup