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: <000000000000b1536a05fe7cf8d7@google.com>
Date:   Mon, 19 Jun 2023 08:13:05 -0700
From:   syzbot <syzbot+733c8795eb2aa33f16ea@...kaller.appspotmail.com>
To:     akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
        linux-mm@...ck.org, linux-next@...r.kernel.org,
        sfr@...b.auug.org.au, syzkaller-bugs@...glegroups.com
Subject: [syzbot] [mm?] linux-next boot error: kernel BUG in do_vmi_align_munmap

Hello,

syzbot found the following issue on:

HEAD commit:    47045630bc40 Add linux-next specific files for 20230619
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1234edd3280000
kernel config:  https://syzkaller.appspot.com/x/.config?x=b4d4487f51524098
dashboard link: https://syzkaller.appspot.com/bug?extid=733c8795eb2aa33f16ea
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/25b62e9481a2/disk-47045630.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f91ca35f7434/vmlinux-47045630.xz
kernel image: https://storage.googleapis.com/syzbot-assets/91d5ca09f47f/bzImage-47045630.xz

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

------------[ cut here ]------------
kernel BUG at mm/mmap.c:2439!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 4836 Comm: dhcpcd Not tainted 6.4.0-rc7-next-20230619-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023
RIP: 0010:do_vmi_align_munmap+0xb11/0x15f0 mm/mmap.c:2439
Code: 48 89 c3 e8 91 04 be ff 4c 89 ee 4c 89 e7 e8 f6 ca 44 08 48 85 c0 49 89 c6 74 11 e8 79 04 be ff 4c 39 f3 74 c6 e8 6f 04 be ff <0f> 0b 44 8b 7c 24 34 4c 63 74 24 60 4c 8b 64 24 70 e8 59 04 be ff
RSP: 0018:ffffc9000383fb98 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff88802a2e7900 RCX: 0000000000000000
RDX: ffff888076a68000 RSI: ffffffff81c65fd1 RDI: ffffc9000383fe80
RBP: 0000000000000000 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000001 R12: ffffc9000383fe70
R13: 00007f7c240c1fff R14: ffff88802a2e7500 R15: ffffc9000383fca0
FS:  00007f7c240c2740(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f7c24293b90 CR3: 000000002bd4c000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 do_vmi_munmap+0x26e/0x2c0 mm/mmap.c:2543
 __vm_munmap+0x137/0x3b0 mm/mmap.c:2825
 __do_sys_munmap mm/mmap.c:2850 [inline]
 __se_sys_munmap mm/mmap.c:2847 [inline]
 __x64_sys_munmap+0x62/0x80 mm/mmap.c:2847
 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
RIP: 0033:0x7f7c24293b97
Code: b8 09 00 00 00 0f 05 48 3d 00 f0 ff ff 76 0c f7 d8 89 05 dc 46 01 00 48 83 c8 ff c3 0f 1f 80 00 00 00 00 b8 0b 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8d 0d b9 46 01 00 f7 d8 89 01 48 83
RSP: 002b:00007ffc3b8cb328 EFLAGS: 00000206 ORIG_RAX: 000000000000000b
RAX: ffffffffffffffda RBX: 000055a934fd0e30 RCX: 00007f7c24293b97
RDX: 00007ffc3b8cb270 RSI: 0000000000004030 RDI: 00007f7c240bd000
RBP: 00007ffc3b8cb420 R08: 00007ffc3b8cb270 R09: 00007ffc3b8cb350
R10: 00007ffc3b8cb2b0 R11: 0000000000000206 R12: 00007f7c242a7000
R13: 0000000000000000 R14: 000055a934fd0e30 R15: 0000000000000000
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:do_vmi_align_munmap+0xb11/0x15f0 mm/mmap.c:2439
Code: 48 89 c3 e8 91 04 be ff 4c 89 ee 4c 89 e7 e8 f6 ca 44 08 48 85 c0 49 89 c6 74 11 e8 79 04 be ff 4c 39 f3 74 c6 e8 6f 04 be ff <0f> 0b 44 8b 7c 24 34 4c 63 74 24 60 4c 8b 64 24 70 e8 59 04 be ff
RSP: 0018:ffffc9000383fb98 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff88802a2e7900 RCX: 0000000000000000
RDX: ffff888076a68000 RSI: ffffffff81c65fd1 RDI: ffffc9000383fe80
RBP: 0000000000000000 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000001 R12: ffffc9000383fe70
R13: 00007f7c240c1fff R14: ffff88802a2e7500 R15: ffffc9000383fca0
FS:  00007f7c240c2740(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f7c24293b90 CR3: 000000002bd4c000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
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.

If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to change 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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ