All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+6f16df7b5a49f0e01b18@syzkaller.appspotmail.com>
To: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	pbonzini@redhat.com,  syzkaller-bugs@googlegroups.com
Subject: [syzbot] [kvm?] BUG: unable to handle kernel paging request in kvm_gmem_get_folio
Date: Fri, 16 Jan 2026 07:08:26 -0800	[thread overview]
Message-ID: <696a546a.050a0220.58bed.0056.GAE@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    9b7977f9e39b Add linux-next specific files for 20260115
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=10585522580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=9c0b39f55c418575
dashboard link: https://syzkaller.appspot.com/bug?extid=6f16df7b5a49f0e01b18
compiler:       Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/32edced7b806/disk-9b7977f9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/dec5450e284a/vmlinux-9b7977f9.xz
kernel image: https://storage.googleapis.com/syzbot-assets/65783c99fb65/bzImage-9b7977f9.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+6f16df7b5a49f0e01b18@syzkaller.appspotmail.com

BUG: unable to handle page fault for address: fffffffffffffffc
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD e143067 P4D e143067 PUD e145067 PMD 0 
Oops: Oops: 0000 [#1] SMP KASAN PTI
CPU: 0 UID: 0 PID: 10212 Comm: syz.7.1148 Tainted: G             L      syzkaller #0 PREEMPT(full) 
Tainted: [L]=SOFTLOCKUP
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
RIP: 0010:const_folio_flags include/linux/page-flags.h:351 [inline]
RIP: 0010:folio_test_head include/linux/page-flags.h:844 [inline]
RIP: 0010:folio_test_large include/linux/page-flags.h:865 [inline]
RIP: 0010:folio_order include/linux/mm.h:1248 [inline]
RIP: 0010:kvm_gmem_get_folio+0x12e/0x240 virt/kvm/guest_memfd.c:147
Code: 00 eb 0d e8 a4 85 80 00 4c 89 f7 e8 6c bc e3 00 4c 8d 73 08 4c 89 f0 48 c1 e8 03 42 80 3c 28 00 74 08 4c 89 f7 e8 b2 5a e7 00 <4d> 8b 36 4c 89 f6 48 83 e6 01 31 ff e8 51 8a 80 00 49 83 e6 01 0f
RSP: 0018:ffffc900031a7cc8 EFLAGS: 00010246
RAX: 1fffffffffffffff RBX: fffffffffffffff4 RCX: 0000000000080000
RDX: ffffc90013fee000 RSI: 000000000007ffff RDI: 0000000000080000
RBP: 1ffff1100d33380f R08: ffff8880b8640dc3 R09: 1ffff110170c81b8
R10: dffffc0000000000 R11: ffffed10170c81b9 R12: ffff88806999c078
R13: dffffc0000000000 R14: fffffffffffffffc R15: 0000000000111e97
FS:  00007fc8a8bb26c0(0000) GS:ffff8881259ad000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: fffffffffffffffc CR3: 000000007db00000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000001
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 kvm_gmem_allocate virt/kvm/guest_memfd.c:276 [inline]
 kvm_gmem_fallocate+0x396/0x840 virt/kvm/guest_memfd.c:316
 vfs_fallocate+0x669/0x7e0 fs/open.c:340
 ksys_fallocate fs/open.c:364 [inline]
 __do_sys_fallocate fs/open.c:369 [inline]
 __se_sys_fallocate fs/open.c:367 [inline]
 __x64_sys_fallocate+0xc0/0x110 fs/open.c:367
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xec/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fc8a7d8f749
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fc8a8bb2038 EFLAGS: 00000246 ORIG_RAX: 000000000000011d
RAX: ffffffffffffffda RBX: 00007fc8a7fe6090 RCX: 00007fc8a7d8f749
RDX: 0000000100000000 RSI: 0000000000000001 RDI: 0000000000000007
RBP: 00007fc8a7e13f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000080000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fc8a7fe6128 R14: 00007fc8a7fe6090 R15: 00007ffeb4d2dde8
 </TASK>
Modules linked in:
CR2: fffffffffffffffc
---[ end trace 0000000000000000 ]---
RIP: 0010:const_folio_flags include/linux/page-flags.h:351 [inline]
RIP: 0010:folio_test_head include/linux/page-flags.h:844 [inline]
RIP: 0010:folio_test_large include/linux/page-flags.h:865 [inline]
RIP: 0010:folio_order include/linux/mm.h:1248 [inline]
RIP: 0010:kvm_gmem_get_folio+0x12e/0x240 virt/kvm/guest_memfd.c:147
Code: 00 eb 0d e8 a4 85 80 00 4c 89 f7 e8 6c bc e3 00 4c 8d 73 08 4c 89 f0 48 c1 e8 03 42 80 3c 28 00 74 08 4c 89 f7 e8 b2 5a e7 00 <4d> 8b 36 4c 89 f6 48 83 e6 01 31 ff e8 51 8a 80 00 49 83 e6 01 0f
RSP: 0018:ffffc900031a7cc8 EFLAGS: 00010246
RAX: 1fffffffffffffff RBX: fffffffffffffff4 RCX: 0000000000080000
RDX: ffffc90013fee000 RSI: 000000000007ffff RDI: 0000000000080000
RBP: 1ffff1100d33380f R08: ffff8880b8640dc3 R09: 1ffff110170c81b8
R10: dffffc0000000000 R11: ffffed10170c81b9 R12: ffff88806999c078
R13: dffffc0000000000 R14: fffffffffffffffc R15: 0000000000111e97
FS:  00007fc8a8bb26c0(0000) GS:ffff8881259ad000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: fffffffffffffffc CR3: 000000007db00000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000001
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
   0:	00 eb                	add    %ch,%bl
   2:	0d e8 a4 85 80       	or     $0x8085a4e8,%eax
   7:	00 4c 89 f7          	add    %cl,-0x9(%rcx,%rcx,4)
   b:	e8 6c bc e3 00       	call   0xe3bc7c
  10:	4c 8d 73 08          	lea    0x8(%rbx),%r14
  14:	4c 89 f0             	mov    %r14,%rax
  17:	48 c1 e8 03          	shr    $0x3,%rax
  1b:	42 80 3c 28 00       	cmpb   $0x0,(%rax,%r13,1)
  20:	74 08                	je     0x2a
  22:	4c 89 f7             	mov    %r14,%rdi
  25:	e8 b2 5a e7 00       	call   0xe75adc
* 2a:	4d 8b 36             	mov    (%r14),%r14 <-- trapping instruction
  2d:	4c 89 f6             	mov    %r14,%rsi
  30:	48 83 e6 01          	and    $0x1,%rsi
  34:	31 ff                	xor    %edi,%edi
  36:	e8 51 8a 80 00       	call   0x808a8c
  3b:	49 83 e6 01          	and    $0x1,%r14
  3f:	0f                   	.byte 0xf


---
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@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

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

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

             reply	other threads:[~2026-01-16 15:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-16 15:08 syzbot [this message]
2026-01-16 15:24 ` [syzbot] [kvm?] BUG: unable to handle kernel paging request in kvm_gmem_get_folio Sean Christopherson

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=696a546a.050a0220.58bed.0056.GAE@google.com \
    --to=syzbot+6f16df7b5a49f0e01b18@syzkaller.appspotmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.