Received: by 2002:a05:6358:45e:b0:b5:b6eb:e1f9 with SMTP id 30csp49889rwe; Tue, 30 Aug 2022 20:46:27 -0700 (PDT) X-Google-Smtp-Source: AA6agR4XZu7tmdgZZPNCRE/TAdWPZzGSQfxZVXjzHdJKgpEuJvkRy16C2aTTOm0MJv7ms3nGHgYO X-Received: by 2002:a17:90b:1810:b0:1fd:b639:fd99 with SMTP id lw16-20020a17090b181000b001fdb639fd99mr1301595pjb.78.1661917587503; Tue, 30 Aug 2022 20:46:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1661917587; cv=none; d=google.com; s=arc-20160816; b=Dc0flajjDfN3o7RuwIbz4Y/pN9uA2Pyh6UYy9lcCNDEbrcwHAp3YnGLGd5bHPrYHXz BQv8EYIV36aF5ja8157mrWJElj5Opp/xxcSBzrjIyxIZcEWIY0tG7BpzsH92rjvOHDUo MKFmEVEJZcToxDfwvUmYFLi88xpheaCx/X8krZeaFFPIXwbo5+/UjvxkWe4TlP8NQORZ entpNRUT1iZ507jZWwYefeP1kb+Yui6EoS5865bAJrjrh8F/Ks2ULl5EfRcFRO9OPyEx +daS8y6uu9+sTkv/X2GtNo45CjaX6leIwQ8inqsJt3xy1YPKJAVUX6wuFu+XKqr5gQOm VEcw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=fiOKZnNdxmLYNBXMmqi3GFFdRwsFMJMRCNCo8og41hE=; b=VBZFLUQLTwIdGjJB31LkyEiXJIIltHX8gO7zv/phKZI2+qsRTHTw5sPRnimlTel9Lg tO1ZTTh74XyoJmD3rGWJOYO/laaZjiJXrqs2q1o4lIERAy6PbM8yRR1L4ENfPuOW7sh2 KJ0nULtfLu5jE53tTacdO/vQeZ4QGSEgjy6bOfndjpmAdDq0BjTRP9WwLIT8QUJxpnQh zQvsDnYFjBVRqdGSBtqBhRsimv+xAK5iGFvvH6SN1Cfj8gvBTCeW0kYeIWH+ExhPkijT G1t8dxggH8lFAMlySvOWatSOJwvcX3N87jCY4jO71Fkh6616t9DxrX8SWZ33YiAW4/Uf U0tA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=E5sLVuRg; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id a9-20020a656049000000b0042aca53ca84si3853543pgp.418.2022.08.30.20.46.16; Tue, 30 Aug 2022 20:46:27 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=E5sLVuRg; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231625AbiHaCov (ORCPT + 99 others); Tue, 30 Aug 2022 22:44:51 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39642 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230188AbiHaCot (ORCPT ); Tue, 30 Aug 2022 22:44:49 -0400 Received: from mail-pf1-x42c.google.com (mail-pf1-x42c.google.com [IPv6:2607:f8b0:4864:20::42c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 650FA193 for ; Tue, 30 Aug 2022 19:44:46 -0700 (PDT) Received: by mail-pf1-x42c.google.com with SMTP id 199so13094906pfz.2 for ; Tue, 30 Aug 2022 19:44:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc; bh=fiOKZnNdxmLYNBXMmqi3GFFdRwsFMJMRCNCo8og41hE=; b=E5sLVuRg4Ke/M/hekHh6NqNyJoXPQnXvAE9dm9Xl+Tp72T4sV2Fq0HVFKUzlJRRmwe 6nxBecHlXvyNVbcGal2R33DWmh7Z2usuupIFftXcPjvQtqIvWRH/0ZTqWF7NryJOaBvs zMmpyWa2GCI7qvVqNtYwueh4zIz6HzleTiSD0Q30O/aV7WmNyQ+JJnpUlc9IybGycBC3 EleuV082Hr32YeAju4zzyFgcsGrGlvl2zFr1csLdOc+l0euoxmIoNH+C0FFBGkB3CNOX XPDzWse6gM0S9L6dt+Z6UAq4Pe/fEP/Zynan0zAps7SfbnFaoTqsVww7tbvw2xl2njzD HY8g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-message-state:from:to:cc; bh=fiOKZnNdxmLYNBXMmqi3GFFdRwsFMJMRCNCo8og41hE=; b=DErEX/6jEGhXHaJzYTLSSUvqWi4OfvLNCyd4LocP57VKllFxVpPalrWtbo3w/nUPUa w7u9YvaoEmzEtUlHnZgV6xAQCA0TL4VoC71AwTi2jJe3oeS4/8t0na2utZfRgUHcy8dZ QucuH6WNUKawevy1nqFREiUaUhlAWDe/ysyAcTdbef6PR8MIrRKiVde3TrE18WnmYVEN D5f4SQiI/YwX+uRMrhSBNJLcxtG7OfM1fjt90rq/wth52I/3QM/DYnD9LwsMIKg9d5GQ Gbg6SZyrA9x8J71I3E9MLaMi3Z7Tt1BDFYAZBX6Knf+vtagmcH2BQ6+omSy7hjEFo2u3 hmew== X-Gm-Message-State: ACgBeo2D4LWYaJXYL8lJ2EEznVPdQSlNdYq3QDf38EohlL2SSb+Hnw3N WapmShlIJD06pdQBfgKyLuY= X-Received: by 2002:a05:6a00:804:b0:52f:43f9:b634 with SMTP id m4-20020a056a00080400b0052f43f9b634mr24307126pfk.62.1661913885905; Tue, 30 Aug 2022 19:44:45 -0700 (PDT) Received: from localhost ([36.112.86.8]) by smtp.gmail.com with ESMTPSA id c73-20020a621c4c000000b00536779d43e7sm9997205pfc.201.2022.08.30.19.44.44 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 30 Aug 2022 19:44:45 -0700 (PDT) From: Hawkins Jiawei To: syzbot+5f8dcabe4a3b2c51c607@syzkaller.appspotmail.com, Anton Altaparmakov Cc: akpm@linux-foundation.org, chenxiaosong2@huawei.com, linux-kernel@vger.kernel.org, linux-ntfs-dev@lists.sourceforge.net, syzkaller-bugs@googlegroups.com, yin31149@gmail.com, 18801353760@163.com Subject: [PATCH 1/3] ntfs: fix use-after-free in ntfs_attr_find() Date: Wed, 31 Aug 2022 10:43:34 +0800 Message-Id: <44b15fb54dbc5b5d8c8726e957d494d38538789e.1661875711.git.yin31149@gmail.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Syzkaller reported use-after-free read as follows: ================================================================== BUG: KASAN: use-after-free in ntfs_attr_find+0xc02/0xce0 fs/ntfs/attrib.c:597 Read of size 2 at addr ffff88807e352009 by task syz-executor153/3607 [...] Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106 print_address_description mm/kasan/report.c:317 [inline] print_report.cold+0x2ba/0x719 mm/kasan/report.c:433 kasan_report+0xb1/0x1e0 mm/kasan/report.c:495 ntfs_attr_find+0xc02/0xce0 fs/ntfs/attrib.c:597 ntfs_attr_lookup+0x1056/0x2070 fs/ntfs/attrib.c:1193 ntfs_read_inode_mount+0x89a/0x2580 fs/ntfs/inode.c:1845 ntfs_fill_super+0x1799/0x9320 fs/ntfs/super.c:2854 mount_bdev+0x34d/0x410 fs/super.c:1400 legacy_get_tree+0x105/0x220 fs/fs_context.c:610 vfs_get_tree+0x89/0x2f0 fs/super.c:1530 do_new_mount fs/namespace.c:3040 [inline] path_mount+0x1326/0x1e20 fs/namespace.c:3370 do_mount fs/namespace.c:3383 [inline] __do_sys_mount fs/namespace.c:3591 [inline] __se_sys_mount fs/namespace.c:3568 [inline] __x64_sys_mount+0x27f/0x300 fs/namespace.c:3568 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd [...] The buggy address belongs to the physical page: page:ffffea0001f8d400 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x7e350 head:ffffea0001f8d400 order:3 compound_mapcount:0 compound_pincount:0 flags: 0xfff00000010200(slab|head|node=0|zone=1|lastcpupid=0x7ff) raw: 00fff00000010200 0000000000000000 dead000000000122 ffff888011842140 raw: 0000000000000000 0000000000040004 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: ffff88807e351f00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ffff88807e351f80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc >ffff88807e352000: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ^ ffff88807e352080: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff88807e352100: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ================================================================== Kernel will loads $MFT/$DATA's first mft record in ntfs_read_inode_mount(). Yet the problem is that after loading, kernel doesn't check whether attrs_offset field is a valid value. To be more specific, if attrs_offset field is larger than bytes_allocated field, then it may trigger the out-of-bounds read bug(reported as use-after-free bug) in ntfs_attr_find(), when kernel tries to access the corresponding mft record's attribute. This patch solves it by adding the sanity check between attrs_offset field and bytes_allocated field, after loading the first mft record. Reported-and-tested-by: syzbot+5f8dcabe4a3b2c51c607@syzkaller.appspotmail.com Signed-off-by: Hawkins Jiawei --- fs/ntfs/inode.c | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/fs/ntfs/inode.c b/fs/ntfs/inode.c index db0f1995aedd..08c659332e26 100644 --- a/fs/ntfs/inode.c +++ b/fs/ntfs/inode.c @@ -1829,6 +1829,13 @@ int ntfs_read_inode_mount(struct inode *vi) goto err_out; } + /* Sanity check offset to the first attribute */ + if (le16_to_cpu(m->attrs_offset) >= le32_to_cpu(m->bytes_allocated)) { + ntfs_error(sb, "Incorrect mft offset to the first attribute %u in superblock.", + le16_to_cpu(m->attrs_offset)); + goto err_out; + } + /* Need this to sanity check attribute list references to $MFT. */ vi->i_generation = ni->seq_no = le16_to_cpu(m->sequence_number); -- 2.25.1