linux-kernel - [syzbot] [reiserfs?] memory leak in journal

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <000000000000ffe48405f0681eea@google.com>
Date:   Thu, 22 Dec 2022 02:27:50 -0800
From:   syzbot <syzbot+38daa8d09e2bde63614c@...kaller.appspotmail.com>
To:     akpm@...ux-foundation.org, axboe@...nel.dk, bvanassche@....org,
        jlayton@...nel.org, linux-kernel@...r.kernel.org,
        reiserfs-devel@...r.kernel.org, syzkaller-bugs@...glegroups.com,
        willy@...radead.org, yi.zhang@...wei.com
Subject: [syzbot] [reiserfs?] memory leak in journal_init

Hello,

syzbot found the following issue on:

HEAD commit:    f9ff5644bcc0 Merge tag 'hsi-for-6.2' of git://git.kernel.o..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=168fd1f0480000
kernel config:  https://syzkaller.appspot.com/x/.config?x=ea51bad86b095bab
dashboard link: https://syzkaller.appspot.com/bug?extid=38daa8d09e2bde63614c
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=1427ed10480000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1340b05f880000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/5afa364baa22/disk-f9ff5644.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/eceb2cb98557/vmlinux-f9ff5644.xz
kernel image: https://storage.googleapis.com/syzbot-assets/974bb6f9809b/bzImage-f9ff5644.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/395742fd36dd/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+38daa8d09e2bde63614c@...kaller.appspotmail.com

BUG: memory leak
unreferenced object 0xffff88810c37aa80 (size 192):
  comm "syz-executor428", pid 5076, jiffies 4294957825 (age 12.820s)
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 04 00 00 00 00 00 00 00  ................
    01 00 00 00 00 00 00 00 01 00 00 00 03 00 00 00  ................
  backtrace:
    [<ffffffff814f8270>] kmalloc_trace+0x20/0x90 mm/slab_common.c:1062
    [<ffffffff8178f011>] kmalloc include/linux/slab.h:580 [inline]
    [<ffffffff8178f011>] kzalloc include/linux/slab.h:720 [inline]
    [<ffffffff8178f011>] alloc_journal_list+0x21/0xc0 fs/reiserfs/journal.c:2571
    [<ffffffff8179311f>] journal_list_init fs/reiserfs/journal.c:2585 [inline]
    [<ffffffff8179311f>] journal_init+0x7bf/0x1fc0 fs/reiserfs/journal.c:2840
    [<ffffffff8177e93f>] reiserfs_fill_super+0x61f/0x15d0 fs/reiserfs/super.c:2022
    [<ffffffff8160e263>] mount_bdev+0x223/0x260 fs/super.c:1359
    [<ffffffff8167270b>] legacy_get_tree+0x2b/0x90 fs/fs_context.c:610
    [<ffffffff8160bde8>] vfs_get_tree+0x28/0x100 fs/super.c:1489
    [<ffffffff8164fc87>] do_new_mount fs/namespace.c:3145 [inline]
    [<ffffffff8164fc87>] path_mount+0xc37/0x10d0 fs/namespace.c:3475
    [<ffffffff816508be>] do_mount fs/namespace.c:3488 [inline]
    [<ffffffff816508be>] __do_sys_mount fs/namespace.c:3697 [inline]
    [<ffffffff816508be>] __se_sys_mount fs/namespace.c:3674 [inline]
    [<ffffffff816508be>] __x64_sys_mount+0x18e/0x1d0 fs/namespace.c:3674
    [<ffffffff8489f645>] do_syscall_x64 arch/x86/entry/common.c:50 [inline]
    [<ffffffff8489f645>] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
    [<ffffffff84a00087>] 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@...glegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches