[Android 5.15] BUG: unable to handle kernel paging request in swake_up_locked (2)

0 views
Skip to first unread message

syzbot

unread,
Feb 5, 2026, 11:49:25 PM (17 hours ago) Feb 5
to syzkaller-a...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 4115628a19d7 Merge eb204a6d8bad ("NFS: trace: show TIMEDOU..
git tree: android13-5.15-lts
console output: https://syzkaller.appspot.com/x/log.txt?x=1486ea5a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=deffac0a782f1cb0
dashboard link: https://syzkaller.appspot.com/bug?extid=47d1799dedf1a27ab54a
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15b0ba5a580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10376d3a580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7cc2118f824c/disk-4115628a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d7bfafcd16dd/vmlinux-4115628a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/3b7c9050173e/bzImage-4115628a.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/6627246689eb/mount_13.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=17f64a5a580000)

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

input: syz1 as /devices/virtual/input/input241
BUG: unable to handle page fault for address: fffffffffffffff8
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD 6612067 P4D 6612067 PUD 6614067 PMD 0
Oops: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 1124 Comm: syz.6.255 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/24/2026
RIP: 0010:swake_up_locked+0x57/0x120 kernel/sched/swait.c:30
Code: 89 f7 e8 5c 2c 5b 00 49 8b 1e 4c 39 f3 0f 84 ca 00 00 00 48 8d 7b f8 48 89 f8 48 c1 e8 03 42 80 3c 20 00 74 05 e8 39 2c 5b 00 <48> 8b 7b f8 e8 50 10 fa ff 48 89 df e8 98 83 06 01 84 c0 74 6a 48
RSP: 0018:ffffc9000203fce0 EFLAGS: 00010046
RAX: 1fffffffffffffff RBX: 0000000000000000 RCX: 0000000000000001
RDX: dffffc0000000000 RSI: 0000000000000004 RDI: fffffffffffffff8
RBP: ffffc9000203fd08 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffff52000407f90 R12: dffffc0000000000
R13: 1ffff9200041ef4e R14: ffffc900020f7a80 R15: ffffc900020f7a70
FS: 00007f3f893c76c0(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: fffffffffffffff8 CR3: 0000000124412000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
complete+0x5e/0xb0 kernel/sched/completion.c:36
uinput_flush_requests drivers/input/misc/uinput.c:213 [inline]
uinput_destroy_device+0x129/0x8e0 drivers/input/misc/uinput.c:298
uinput_release+0x3e/0x50 drivers/input/misc/uinput.c:758
__fput+0x20b/0x8b0 fs/file_table.c:311
____fput+0x15/0x20 fs/file_table.c:339
task_work_run+0x127/0x190 kernel/task_work.c:188
tracehook_notify_resume include/linux/tracehook.h:189 [inline]
exit_to_user_mode_loop+0xd0/0xe0 kernel/entry/common.c:181
exit_to_user_mode_prepare+0x87/0xd0 kernel/entry/common.c:214
__syscall_exit_to_user_mode_work kernel/entry/common.c:296 [inline]
syscall_exit_to_user_mode+0x1a/0x30 kernel/entry/common.c:307
do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f3f89562eb9
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f3f893c7028 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4
RAX: 0000000000000000 RBX: 00007f3f897ddfa0 RCX: 00007f3f89562eb9
RDX: 0000000000000000 RSI: ffffffffffffffff RDI: 0000000000000003
RBP: 00007f3f895d0c1f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f3f897de038 R14: 00007f3f897ddfa0 R15: 00007fff37f94bc8
</TASK>
Modules linked in:
CR2: fffffffffffffff8
---[ end trace 62e25af946395276 ]---
RIP: 0010:swake_up_locked+0x57/0x120 kernel/sched/swait.c:30
Code: 89 f7 e8 5c 2c 5b 00 49 8b 1e 4c 39 f3 0f 84 ca 00 00 00 48 8d 7b f8 48 89 f8 48 c1 e8 03 42 80 3c 20 00 74 05 e8 39 2c 5b 00 <48> 8b 7b f8 e8 50 10 fa ff 48 89 df e8 98 83 06 01 84 c0 74 6a 48
RSP: 0018:ffffc9000203fce0 EFLAGS: 00010046
RAX: 1fffffffffffffff RBX: 0000000000000000 RCX: 0000000000000001
RDX: dffffc0000000000 RSI: 0000000000000004 RDI: fffffffffffffff8
RBP: ffffc9000203fd08 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffff52000407f90 R12: dffffc0000000000
R13: 1ffff9200041ef4e R14: ffffc900020f7a80 R15: ffffc900020f7a70
FS: 00007f3f893c76c0(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: fffffffffffffff8 CR3: 0000000124412000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 89 f7 mov %esi,%edi
2: e8 5c 2c 5b 00 call 0x5b2c63
7: 49 8b 1e mov (%r14),%rbx
a: 4c 39 f3 cmp %r14,%rbx
d: 0f 84 ca 00 00 00 je 0xdd
13: 48 8d 7b f8 lea -0x8(%rbx),%rdi
17: 48 89 f8 mov %rdi,%rax
1a: 48 c1 e8 03 shr $0x3,%rax
1e: 42 80 3c 20 00 cmpb $0x0,(%rax,%r12,1)
23: 74 05 je 0x2a
25: e8 39 2c 5b 00 call 0x5b2c63
* 2a: 48 8b 7b f8 mov -0x8(%rbx),%rdi <-- trapping instruction
2e: e8 50 10 fa ff call 0xfffa1083
33: 48 89 df mov %rbx,%rdi
36: e8 98 83 06 01 call 0x10683d3
3b: 84 c0 test %al,%al
3d: 74 6a je 0xa9
3f: 48 rex.W


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

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 all
Reply to author
Forward
0 new messages