linux-kernel - Re: [syzbot] [dri?] [reiserfs?] WARNING: bad unlock balance in vkms_vblank

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: <000000000000c6570d0602e1d030@google.com>
Date:   Mon, 14 Aug 2023 06:12:33 -0700
From:   syzbot <syzbot+5671b8bcd5178fe56c23@...kaller.appspotmail.com>
To:     hdanton@...a.com, linux-kernel@...r.kernel.org,
        syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [dri?] [reiserfs?] WARNING: bad unlock balance in vkms_vblank_simulate

Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
BUG: unable to handle kernel paging request in corrupted

BUG: unable to handle page fault for address: 000000000000ff01
#PF: supervisor instruction fetch in kernel mode
#PF: error_code(0x0010) - not-present page
PGD 68064067 P4D 68064067 PUD 6806d067 PMD 0 
Oops: 0010 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 5037 Comm: kworker/1:3 Not tainted 6.5.0-rc5-next-20230808-syzkaller-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023
Workqueue:  0x0 (events)
RIP: 0010:0xff01
Code: Unable to access opcode bytes at 0xfed7.
RSP: 0018:ffffc90003b2fc60 EFLAGS: 00010086
RAX: ffff888024685940 RBX: 000000000000ff01 RCX: 0000000000000000
RDX: ffff888021963b80 RSI: ffffffff812d721d RDI: 0000000000000007
RBP: 0000000100040020 R08: 0000000000000007 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000100040020
R13: 000000000000ff01 R14: 0000000100040020 R15: 000000000000ff01
FS:  0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000000ff01 CR3: 000000001ef98000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 </TASK>
Modules linked in:
CR2: 000000000000ff01
---[ end trace 0000000000000000 ]---
RIP: 0010:0xff01
Code: Unable to access opcode bytes at 0xfed7.
RSP: 0018:ffffc90003b2fc60 EFLAGS: 00010086

RAX: ffff888024685940 RBX: 000000000000ff01 RCX: 0000000000000000
RDX: ffff888021963b80 RSI: ffffffff812d721d RDI: 0000000000000007
RBP: 0000000100040020 R08: 0000000000000007 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000100040020
R13: 000000000000ff01 R14: 0000000100040020 R15: 000000000000ff01
FS:  0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000000ff01 CR3: 000000001ef98000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


Tested on:

commit:         71cd4fc4 Add linux-next specific files for 20230808
git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
console output: https://syzkaller.appspot.com/x/log.txt?x=166b9763a80000
kernel config:  https://syzkaller.appspot.com/x/.config?x=e36b5ba725f7349d
dashboard link: https://syzkaller.appspot.com/bug?extid=5671b8bcd5178fe56c23
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=10060e27a80000