From: syzbot <syzbot+237f670105a254a230d4@syzkaller.appspotmail.com>
To: boqun@kernel.org, linux-kernel@vger.kernel.org,
mathieu.desnoyers@efficios.com, paulmck@kernel.org,
peterz@infradead.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kernel?] BUG: unable to handle kernel paging request in write_comp_data
Date: Mon, 14 Sep 2026 15:11:29 -0700 [thread overview]
Message-ID: <6aa87111.f81106d8.2ab401.0057.GAE@google.com> (raw)
In-Reply-To: <6a6ecd0c.6ce73036.24301b.001c.GAE@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: 704340f1cd0d Merge tag 'x86_urgent_for_7.3-rc4' of git://g..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=13351925580000
kernel config: https://syzkaller.appspot.com/x/.config?x=8c5c3949d762a91f
dashboard link: https://syzkaller.appspot.com/bug?extid=237f670105a254a230d4
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11b875f9580000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+237f670105a254a230d4@syzkaller.appspotmail.com
BUG: unable to handle page fault for address: ffffc90003792fe8
#PF: supervisor write access in kernel mode
#PF: error_code(0x0002) - not-present page
PGD 1c000067 P4D 1c000067 PUD 1d695067 PMD 25aa1067 PTE 0
Oops: Oops: 0002 [#1] SMP KASAN NOPTI
CPU: 2 UID: 0 PID: 6034 Comm: syz-executor404 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
RIP: 0010:write_comp_data+0x7c/0xa0 kernel/kcov.c:263
Code: 00 8b bf 14 17 00 00 48 8b 30 48 c1 e7 03 4c 8d 1c b5 00 00 00 00 4a 8d 14 dd 28 00 00 00 48 39 d7 72 1b 48 83 c6 01 48 89 30 <4c> 89 44 10 e0 4c 89 4c 10 e8 4c 89 54 10 f0 4a 89 4c d8 20 e9 9b
RSP: 0018:ffffc900016cfec0 EFLAGS: 00010257
RAX: ffffc90003793000 RBX: 0000000000000000 RCX: ffffffff824af562
RDX: 0000000000000008 RSI: 0000000000000000 RDI: 0000000000002000
RBP: 0000000000000000 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000000000000 R11: fffffffffffffffc R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
FS: 000055556039d400(0000) GS:ffff8880d5d59000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffc90003792fe8 CR3: 0000000033822000 CR4: 0000000000352ef0
Call Trace:
<TASK>
__do_sys_rseq kernel/rseq.c:549 [inline]
__se_sys_rseq kernel/rseq.c:547 [inline]
__x64_sys_rseq+0xc2/0x2e0 kernel/rseq.c:547
do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
do_syscall_64+0x123/0x790 arch/x86/entry/syscall_64.c:84
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f4f6e875649
Code: c0 79 93 eb d5 48 8d 7c 1d 00 eb 99 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 d8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fffe975f1b8 EFLAGS: 00000246 ORIG_RAX: 000000000000014e
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f4f6e875649
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 00007f4f6e846000 R08: 0000000000000000 R09: 00000000000a8ca8
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fffe975f2e8
R13: 0000000000000002 R14: 00007f4f6e8f8cc0 R15: 0000000000000002
</TASK>
Modules linked in:
CR2: ffffc90003792fe8
---[ end trace 0000000000000000 ]---
RIP: 0010:write_comp_data+0x7c/0xa0 kernel/kcov.c:263
Code: 00 8b bf 14 17 00 00 48 8b 30 48 c1 e7 03 4c 8d 1c b5 00 00 00 00 4a 8d 14 dd 28 00 00 00 48 39 d7 72 1b 48 83 c6 01 48 89 30 <4c> 89 44 10 e0 4c 89 4c 10 e8 4c 89 54 10 f0 4a 89 4c d8 20 e9 9b
RSP: 0018:ffffc900016cfec0 EFLAGS: 00010257
RAX: ffffc90003793000 RBX: 0000000000000000 RCX: ffffffff824af562
RDX: 0000000000000008 RSI: 0000000000000000 RDI: 0000000000002000
RBP: 0000000000000000 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000000000000 R11: fffffffffffffffc R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
FS: 000055556039d400(0000) GS:ffff8880d5d59000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffc90003792fe8 CR3: 0000000033822000 CR4: 0000000000352ef0
----------------
Code disassembly (best guess):
0: 00 8b bf 14 17 00 add %cl,0x1714bf(%rbx)
6: 00 48 8b add %cl,-0x75(%rax)
9: 30 48 c1 xor %cl,-0x3f(%rax)
c: e7 03 out %eax,$0x3
e: 4c 8d 1c b5 00 00 00 lea 0x0(,%rsi,4),%r11
15: 00
16: 4a 8d 14 dd 28 00 00 lea 0x28(,%r11,8),%rdx
1d: 00
1e: 48 39 d7 cmp %rdx,%rdi
21: 72 1b jb 0x3e
23: 48 83 c6 01 add $0x1,%rsi
27: 48 89 30 mov %rsi,(%rax)
* 2a: 4c 89 44 10 e0 mov %r8,-0x20(%rax,%rdx,1) <-- trapping instruction
2f: 4c 89 4c 10 e8 mov %r9,-0x18(%rax,%rdx,1)
34: 4c 89 54 10 f0 mov %r10,-0x10(%rax,%rdx,1)
39: 4a 89 4c d8 20 mov %rcx,0x20(%rax,%r11,8)
3e: e9 .byte 0xe9
3f: 9b fwait
---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
next prev parent reply other threads:[~2026-09-14 22:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-02 4:52 syzbot
2026-09-14 22:11 ` syzbot [this message]
2026-09-15 2:06 ` Edward Adam Davis
2026-09-15 3:24 ` syzbot
2026-09-15 3:33 ` [PATCH] kcov: add a missing bound check in write_comp_data() Edward Adam Davis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6aa87111.f81106d8.2ab401.0057.GAE@google.com \
--to=syzbot+237f670105a254a230d4@syzkaller.appspotmail.com \
--cc=boqun@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®