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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 13 Nov 2020 09:17:31 -0800
From:   syzbot <>
Subject: memory leak in generic_parse_monolithic


syzbot found the following issue on:

HEAD commit:    af5043c8 Merge tag 'acpi-5.10-rc4' of git://
git tree:       upstream
console output:
kernel config:
dashboard link:
compiler:       gcc (GCC) 10.1.0-syz 20200507
syz repro:
C reproducer:

IMPORTANT: if you fix the issue, please add the following tag to the commit:

Warning: Permanently added '' (ECDSA) to the list of known hosts.
executing program
executing program
BUG: memory leak
unreferenced object 0xffff888111f15a80 (size 32):
  comm "syz-executor841", pid 8507, jiffies 4294942125 (age 14.070s)
  hex dump (first 32 bytes):
    25 5e 5d 24 5b 2b 25 5d 28 24 7b 3a 0f 6b 5b 29  %^]$[+%](${:.k[)
    2d 3a 00 00 00 00 00 00 00 00 00 00 00 00 00 00  -:..............
    [<000000005c6f565d>] kmemdup_nul+0x2d/0x70 mm/util.c:151
    [<0000000054985c27>] vfs_parse_fs_string+0x6e/0xd0 fs/fs_context.c:155
    [<0000000077ef66e4>] generic_parse_monolithic+0xe0/0x130 fs/fs_context.c:201
    [<00000000d4d4a652>] do_new_mount fs/namespace.c:2871 [inline]
    [<00000000d4d4a652>] path_mount+0xbbb/0x1170 fs/namespace.c:3205
    [<00000000f43f0071>] do_mount fs/namespace.c:3218 [inline]
    [<00000000f43f0071>] __do_sys_mount fs/namespace.c:3426 [inline]
    [<00000000f43f0071>] __se_sys_mount fs/namespace.c:3403 [inline]
    [<00000000f43f0071>] __x64_sys_mount+0x18e/0x1d0 fs/namespace.c:3403
    [<00000000dc5fffd5>] do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
    [<000000004e665669>] entry_SYSCALL_64_after_hwframe+0x44/0xa9

This report is generated by a bot. It may contain errors.
See for more information about syzbot.
syzbot engineers can be reached at

syzbot will keep track of this issue. See: for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:

Powered by blists - more mailing lists