Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp3207881imm; Sun, 3 Jun 2018 22:38:04 -0700 (PDT) X-Google-Smtp-Source: ADUXVKJu38981LSbVdus4iWZA7tgVFxA9ecD6kZL2y07KdTuL5gqTbRvFygPg8c911bH21absbxD X-Received: by 2002:a62:3dca:: with SMTP id x71-v6mr20000981pfj.134.1528090684320; Sun, 03 Jun 2018 22:38:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1528090684; cv=none; d=google.com; s=arc-20160816; b=gXyZoXNvTQiFDlTFmP4PDUB8T42iUPK2/GFhn3lvP3hUYfj0DsH53IW1zqm3t8i5nZ Qml+NtHBkRgVehJzNuYsqu96vKwxVlVzOwSPU2DejKyww2C3+jpMmzSj5svZ5QR6Udnc Y2TjaNg5hBFDzoMj07NN168wCgjAsQoPlKW/N+X6lmWDtiizTtTnzII1sVWhR8fw6ZAK 6TMlAgxKhrx6zSqXMZ+X0JuHk+NCv6VivUXXrUKtZwO6P+fYFyhhZUiWtYci5M/3WK2K IXPCID9NDFppVTmb6z8nEidkJfQWMjoduMHK+Svk1r525rvg3EGd3vm2cskuv2by+pYN w6OQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=tePCeuduR1tYOblQqfgQHtjsVPhd0662wv8xfsqKhzI=; b=fFcrxMZ/5O09q9fuLyArhCKZMgiU/cdI9amr+QYjuCiwXXnjukkv7bUgl9QYeY99/1 Ir5ZdPN/Z63NqNNTMglMM8zrFSFS9TpBrz3O6aZtQ2pYBFHqdG4+Ui5eqNWttJLaBHQ6 1qgnkjxevH88XHNawwoW3QyAX2vB6ihLmpI3YO/mmfn3wQFfwjwY2cPqK98o8JgV7FC0 yxeHh2zT65RbvLSBq2P9k3+lfdR2ZoUOc1VEx1Akw7JT6CYeq0murCbkjjkQl0I9TS94 pKs92DctUzXV3JtdvgW+0Oi6yJA6gB9uahWAtU981Zx0bk9ED0CfBcOPl/gPDcRB87du yR8g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=SHle+Si5; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q23-v6si5822585pgc.209.2018.06.03.22.37.49; Sun, 03 Jun 2018 22:38:04 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=SHle+Si5; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751624AbeFDFhU (ORCPT + 99 others); Mon, 4 Jun 2018 01:37:20 -0400 Received: from mail-pl0-f68.google.com ([209.85.160.68]:46381 "EHLO mail-pl0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750997AbeFDFhS (ORCPT ); Mon, 4 Jun 2018 01:37:18 -0400 Received: by mail-pl0-f68.google.com with SMTP id 30-v6so18952757pld.13 for ; Sun, 03 Jun 2018 22:37:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=tePCeuduR1tYOblQqfgQHtjsVPhd0662wv8xfsqKhzI=; b=SHle+Si5V+CcoPK+TdnaSlnsAMxh73pIfXj7WJtfFJPCjueFFD/+06uOCmyyX4LotD K2q3ezA9OMT68Uxvg6he9neTsIgXsNGm3W++yXSQaSPY+5cEHlBbCFOOcJ8CO81lENRe vUDC7Hi2CFeahwoQVgMOKXCXs/kYgz8xA2kFXF3xDJRcaoGIgoY0OBUKVItA14yBik8q 8xciqsy4QabCQ08sLjySDO50zSwZkVhQSY+dsAySeaaMggTAMB25W09AVKPb2eJxLDUA GqUnDrEjW2ILsBQaGZ7VtPdxvkFZ7KpMyqdaMosU32jyXF9mX65FwHCSm6h9PSZDdmEc pkiw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=tePCeuduR1tYOblQqfgQHtjsVPhd0662wv8xfsqKhzI=; b=c27fNwuDtJI3QUwSdvC3M7GKKcnhqvWraomTNz6liN2J2mveaF+FGD9huyRKM7pD2F jkkgtpdjgtNyOidIbAxqgOQjW6dkY/6STa+8LGfhh7FHDEOFGExRqssqmKOBLmiC6bNW nYzRdFAJleX6n7kgRS2URbMideJL28f+lQmtrFsgpiZ92c70OQzVDf0NJYo+WOWk8V5J 7VkPM7exu0FO/leNpMQihWeuY204KQcY8GQFHy7a2cIVU7FpcTifY+9V+s3OyJkboqE7 4FDsy9xUm+RbGTcmogsaeG0wMbdTIxUorvqO5Jp876fOHn0K+D2NraBSht5aFARvw7RN Z1Dw== X-Gm-Message-State: ALKqPweZH517dBYS+p/iLjaEioPeUxJBrNsGcsZKYzZt0ROL+8JsTODQ A+lUROTJqn5dqhDbvcMTjMi+UIWu7L2O7TwdnMNZpg== X-Received: by 2002:a17:902:1566:: with SMTP id b35-v6mr20587171plh.107.1528090637945; Sun, 03 Jun 2018 22:37:17 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a17:90a:d01:0:0:0:0 with HTTP; Sun, 3 Jun 2018 22:36:57 -0700 (PDT) In-Reply-To: <000000000000b2a7ea056dc54779@google.com> References: <000000000000b2a7ea056dc54779@google.com> From: Dmitry Vyukov Date: Mon, 4 Jun 2018 07:36:57 +0200 Message-ID: Subject: Re: KASAN: slab-out-of-bounds Read in bpf_csum_update To: syzbot Cc: Alexei Starovoitov , Daniel Borkmann , David Miller , LKML , netdev , syzkaller-bugs Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jun 4, 2018 at 1:36 AM, syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit: 0512e0134582 Merge tag 'xfs-4.17-fixes-3' of git://git.ker.. > git tree: upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=17eb2d7b800000 > kernel config: https://syzkaller.appspot.com/x/.config?x=968b0b23c7854c0b > dashboard link: https://syzkaller.appspot.com/bug?extid=efae31b384d5badbd620 > compiler: gcc (GCC) 8.0.1 20180413 (experimental) > syzkaller repro:https://syzkaller.appspot.com/x/repro.syz?x=162c6def800000 > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14fe3db7800000 > > IMPORTANT: if you fix the bug, please add the following tag to the commit: > Reported-by: syzbot+efae31b384d5badbd620@syzkaller.appspotmail.com > > random: sshd: uninitialized urandom read (32 bytes read) > random: sshd: uninitialized urandom read (32 bytes read) > random: sshd: uninitialized urandom read (32 bytes read) > random: sshd: uninitialized urandom read (32 bytes read) > ================================================================== > BUG: KASAN: slab-out-of-bounds in ____bpf_csum_update net/core/filter.c:1679 > [inline] > BUG: KASAN: slab-out-of-bounds in bpf_csum_update+0xb4/0xc0 > net/core/filter.c:1673 > Read of size 1 at addr ffff8801d9235b50 by task syz-executor507/4513 > > CPU: 0 PID: 4513 Comm: syz-executor507 Not tainted 4.17.0-rc7+ #78 > Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS > Google 01/01/2011 > Call Trace: > __dump_stack lib/dump_stack.c:77 [inline] > dump_stack+0x1b9/0x294 lib/dump_stack.c:113 > print_address_description+0x6c/0x20b mm/kasan/report.c:256 > kasan_report_error mm/kasan/report.c:354 [inline] > kasan_report.cold.7+0x242/0x2fe mm/kasan/report.c:412 > __asan_report_load1_noabort+0x14/0x20 mm/kasan/report.c:430 > ____bpf_csum_update net/core/filter.c:1679 [inline] > bpf_csum_update+0xb4/0xc0 net/core/filter.c:1673 /\/\/\/\/\ Are there any known bugs with unwind through bpf functions? > Allocated by task 0: > (stack is not available) > > Freed by task 0: > (stack is not available) > > The buggy address belongs to the object at ffff8801d9235a40 > which belongs to the cache skbuff_head_cache of size 232 > The buggy address is located 40 bytes to the right of > 232-byte region [ffff8801d9235a40, ffff8801d9235b28) > The buggy address belongs to the page: > page:ffffea0007648d40 count:1 mapcount:0 mapping:ffff8801d9235040 index:0x0 > flags: 0x2fffc0000000100(slab) > raw: 02fffc0000000100 ffff8801d9235040 0000000000000000 000000010000000c > raw: ffffea00074360a0 ffff8801d944d848 ffff8801d9bdd6c0 0000000000000000 > page dumped because: kasan: bad access detected > > Memory state around the buggy address: > ffff8801d9235a00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc > ffff8801d9235a80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc >> >> ffff8801d9235b00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc > > ^ > ffff8801d9235b80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc > ffff8801d9235c00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc > ================================================================== > > > --- > This bug 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 bug report. See: > https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with > syzbot. > syzbot can test patches for this bug, for details see: > https://goo.gl/tpsmEJ#testing-patches > > -- > You received this message because you are subscribed to the Google Groups > "syzkaller-bugs" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to syzkaller-bugs+unsubscribe@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/syzkaller-bugs/000000000000b2a7ea056dc54779%40google.com. > For more options, visit https://groups.google.com/d/optout.