[Android 5.10] BUG: unable to handle kernel paging request in swake_up_locked (2)
2 views
Skip to first unread message
syzbot
Aug 2, 2025, 4:30:33 AMAug 2
to syzkaller-a...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 1154f779f3f3 Merge android13-5.10 into android13-5.10-lts
git tree: android13-5.10-lts
console output: https://syzkaller.appspot.com/x/log.txt?x=144bf2a2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7b5d720faa3cf893
dashboard link: https://syzkaller.appspot.com/bug?extid=13fa5fb6a02614ef9263
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15a35cf0580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=166c22a2580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/495aa4ff1411/disk-1154f779.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/57b83818ab25/vmlinux-1154f779.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d0608d2c72de/bzImage-1154f779.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/ef55d9cf99a7/mount_2.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=126c22a2580000)
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+13fa5f...@syzkaller.appspotmail.com
BUG: unable to handle page fault for address: fffffffffffffff8
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD 6212067 P4D 6212067 PUD 6214067 PMD 0
Oops: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 2994 Comm: syz.3.535 Not tainted 5.10.240-syzkaller-00225-g1154f779f3f3 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:swake_up_locked+0x57/0x120 kernel/sched/swait.c:30
Code: 89 f7 e8 7c 3e 54 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 59 3e 54 00 <48> 8b 7b f8 e8 00 70 fa ff 48 89 df e8 18 df f3 00 84 c0 74 6a 48
RSP: 0018:ffffc90000d97d48 EFLAGS: 00010046
RAX: 1fffffffffffffff RBX: 0000000000000000 RCX: 0000000000000001
RDX: dffffc0000000000 RSI: 0000000000000004 RDI: fffffffffffffff8
RBP: ffffc90000d97d70 R08: 0000000000000004 R09: 0000000000000003
R10: fffff520001b2f9c R11: 1ffff920001b2f9c R12: dffffc0000000000
R13: 1ffff920001caf56 R14: ffffc90000e57ac0 R15: ffffc90000e57ab0
FS: 0000555558053500(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: fffffffffffffff8 CR3: 0000000115844000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
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+0x2fb/0x770 fs/file_table.c:281
____fput+0x15/0x20 fs/file_table.c:314
task_work_run+0x127/0x190 kernel/task_work.c:189
tracehook_notify_resume include/linux/tracehook.h:188 [inline]
exit_to_user_mode_loop+0xcb/0xe0 kernel/entry/common.c:172
exit_to_user_mode_prepare kernel/entry/common.c:199 [inline]
syscall_exit_to_user_mode+0x68/0x90 kernel/entry/common.c:274
do_syscall_64+0x3d/0x40 arch/x86/entry/common.c:56
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7fdc7b1dfb69
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:00007ffd9089a9f8 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4
RAX: 0000000000000000 RBX: 00000000000778f9 RCX: 00007fdc7b1dfb69
RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003
RBP: 00007fdc7b408ba0 R08: 0000000000000001 R09: 000000109089acef
R10: 00007fdc7b051000 R11: 0000000000000246 R12: 00007fdc7b40708c
R13: 00007fdc7b407080 R14: ffffffffffffffff R15: 00007ffd9089ab10
Modules linked in:
CR2: fffffffffffffff8
---[ end trace 1bbc438ceab401ad ]---
RIP: 0010:swake_up_locked+0x57/0x120 kernel/sched/swait.c:30
Code: 89 f7 e8 7c 3e 54 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 59 3e 54 00 <48> 8b 7b f8 e8 00 70 fa ff 48 89 df e8 18 df f3 00 84 c0 74 6a 48
RSP: 0018:ffffc90000d97d48 EFLAGS: 00010046
RAX: 1fffffffffffffff RBX: 0000000000000000 RCX: 0000000000000001
RDX: dffffc0000000000 RSI: 0000000000000004 RDI: fffffffffffffff8
RBP: ffffc90000d97d70 R08: 0000000000000004 R09: 0000000000000003
R10: fffff520001b2f9c R11: 1ffff920001b2f9c R12: dffffc0000000000
R13: 1ffff920001caf56 R14: ffffc90000e57ac0 R15: ffffc90000e57ab0
FS: 0000555558053500(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: fffffffffffffff8 CR3: 0000000115844000 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 7c 3e 54 00 call 0x543e83
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 59 3e 54 00 call 0x543e83
* 2a: 48 8b 7b f8 mov -0x8(%rbx),%rdi <-- trapping instruction
2e: e8 00 70 fa ff call 0xfffa7033
33: 48 89 df mov %rbx,%rdi
36: e8 18 df f3 00 call 0xf3df53
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
syzbot found the following issue on:
HEAD commit: 1154f779f3f3 Merge android13-5.10 into android13-5.10-lts
git tree: android13-5.10-lts
console output: https://syzkaller.appspot.com/x/log.txt?x=144bf2a2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7b5d720faa3cf893
dashboard link: https://syzkaller.appspot.com/bug?extid=13fa5fb6a02614ef9263
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15a35cf0580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=166c22a2580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/495aa4ff1411/disk-1154f779.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/57b83818ab25/vmlinux-1154f779.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d0608d2c72de/bzImage-1154f779.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/ef55d9cf99a7/mount_2.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=126c22a2580000)
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+13fa5f...@syzkaller.appspotmail.com
BUG: unable to handle page fault for address: fffffffffffffff8
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD 6212067 P4D 6212067 PUD 6214067 PMD 0
Oops: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 2994 Comm: syz.3.535 Not tainted 5.10.240-syzkaller-00225-g1154f779f3f3 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:swake_up_locked+0x57/0x120 kernel/sched/swait.c:30
Code: 89 f7 e8 7c 3e 54 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 59 3e 54 00 <48> 8b 7b f8 e8 00 70 fa ff 48 89 df e8 18 df f3 00 84 c0 74 6a 48
RSP: 0018:ffffc90000d97d48 EFLAGS: 00010046
RAX: 1fffffffffffffff RBX: 0000000000000000 RCX: 0000000000000001
RDX: dffffc0000000000 RSI: 0000000000000004 RDI: fffffffffffffff8
RBP: ffffc90000d97d70 R08: 0000000000000004 R09: 0000000000000003
R10: fffff520001b2f9c R11: 1ffff920001b2f9c R12: dffffc0000000000
R13: 1ffff920001caf56 R14: ffffc90000e57ac0 R15: ffffc90000e57ab0
FS: 0000555558053500(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: fffffffffffffff8 CR3: 0000000115844000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
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+0x2fb/0x770 fs/file_table.c:281
____fput+0x15/0x20 fs/file_table.c:314
task_work_run+0x127/0x190 kernel/task_work.c:189
tracehook_notify_resume include/linux/tracehook.h:188 [inline]
exit_to_user_mode_loop+0xcb/0xe0 kernel/entry/common.c:172
exit_to_user_mode_prepare kernel/entry/common.c:199 [inline]
syscall_exit_to_user_mode+0x68/0x90 kernel/entry/common.c:274
do_syscall_64+0x3d/0x40 arch/x86/entry/common.c:56
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7fdc7b1dfb69
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:00007ffd9089a9f8 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4
RAX: 0000000000000000 RBX: 00000000000778f9 RCX: 00007fdc7b1dfb69
RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003
RBP: 00007fdc7b408ba0 R08: 0000000000000001 R09: 000000109089acef
R10: 00007fdc7b051000 R11: 0000000000000246 R12: 00007fdc7b40708c
R13: 00007fdc7b407080 R14: ffffffffffffffff R15: 00007ffd9089ab10
Modules linked in:
CR2: fffffffffffffff8
---[ end trace 1bbc438ceab401ad ]---
RIP: 0010:swake_up_locked+0x57/0x120 kernel/sched/swait.c:30
Code: 89 f7 e8 7c 3e 54 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 59 3e 54 00 <48> 8b 7b f8 e8 00 70 fa ff 48 89 df e8 18 df f3 00 84 c0 74 6a 48
RSP: 0018:ffffc90000d97d48 EFLAGS: 00010046
RAX: 1fffffffffffffff RBX: 0000000000000000 RCX: 0000000000000001
RDX: dffffc0000000000 RSI: 0000000000000004 RDI: fffffffffffffff8
RBP: ffffc90000d97d70 R08: 0000000000000004 R09: 0000000000000003
R10: fffff520001b2f9c R11: 1ffff920001b2f9c R12: dffffc0000000000
R13: 1ffff920001caf56 R14: ffffc90000e57ac0 R15: ffffc90000e57ab0
FS: 0000555558053500(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: fffffffffffffff8 CR3: 0000000115844000 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 7c 3e 54 00 call 0x543e83
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 59 3e 54 00 call 0x543e83
* 2a: 48 8b 7b f8 mov -0x8(%rbx),%rdi <-- trapping instruction
2e: e8 00 70 fa ff call 0xfffa7033
33: 48 89 df mov %rbx,%rdi
36: e8 18 df f3 00 call 0xf3df53
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