[moderation] [tomoyo?] general protection fault in tomoyo_socket_bind_permission

0 views
Skip to first unread message

syzbot

unread,
Jun 26, 2024, 5:27:27 PM (4 days ago) Jun 26
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 62c97045b8f7 Add linux-next specific files for 20240624
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=10c8351e980000
kernel config: https://syzkaller.appspot.com/x/.config?x=6221d1071c39b052
dashboard link: https://syzkaller.appspot.com/bug?extid=f879b9760ba7ece3387f
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [jmo...@namei.org linux-...@vger.kernel.org linux-secu...@vger.kernel.org pa...@paul-moore.com penguin...@I-love.SAKURA.ne.jp se...@hallyn.com take...@nttdata.co.jp tomoyo...@lists.osdn.me]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a7ae66cd8c7b/disk-62c97045.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/de10688455d9/vmlinux-62c97045.xz
kernel image: https://storage.googleapis.com/syzbot-assets/736a405e9649/bzImage-62c97045.xz

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

Oops: general protection fault, probably for non-canonical address 0xdffffc0000000003: 0000 [#1] PREEMPT SMP KASAN PTI
KASAN: null-ptr-deref in range [0x0000000000000018-0x000000000000001f]
CPU: 1 UID: 0 PID: 8001 Comm: syz.4.488 Not tainted 6.10.0-rc5-next-20240624-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024
RIP: 0010:tomoyo_socket_bind_permission+0xa5/0x340 security/tomoyo/network.c:727
Code: f3 f3 66 43 c7 44 2e 0e f3 f3 e8 66 2b 2d fd ba 30 00 00 00 48 89 df 31 f6 e8 67 d0 93 fd 49 8d 5c 24 18 48 89 d8 48 c1 e8 03 <42> 80 3c 28 00 74 08 48 89 df e8 7c cd 93 fd 48 8b 03 48 89 44 24
RSP: 0018:ffffc90003fd7860 EFLAGS: 00010206
RAX: 0000000000000003 RBX: 0000000000000018 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffc90003fd78d0
RBP: ffffc90003fd7950 R08: ffffc90003fd78cf R09: 0000000000000000
R10: ffffc90003fd78a0 R11: fffff520007faf1a R12: 0000000000000000
R13: dffffc0000000000 R14: 1ffff920007faf10 R15: ffff88802ef450a0
FS: 00007f2c6171f6c0(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b32917ff8 CR3: 0000000078066000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
security_socket_bind+0x75/0xb0 security/security.c:4460
__sys_bind_socket+0x28/0xb0 net/socket.c:1830
io_bind+0x8f/0x190 io_uring/net.c:1752
io_issue_sqe+0x3cf/0x14f0 io_uring/io_uring.c:1674
io_queue_sqe io_uring/io_uring.c:1888 [inline]
io_submit_sqe io_uring/io_uring.c:2144 [inline]
io_submit_sqes+0xaff/0x1bf0 io_uring/io_uring.c:2259
__do_sys_io_uring_enter io_uring/io_uring.c:3168 [inline]
__se_sys_io_uring_enter+0x2d4/0x2670 io_uring/io_uring.c:3105
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f2c60975ae9
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:00007f2c6171f048 EFLAGS: 00000246 ORIG_RAX: 00000000000001aa
RAX: ffffffffffffffda RBX: 00007f2c60b03fa0 RCX: 00007f2c60975ae9
RDX: 0000000000000000 RSI: 0000000000002d3e RDI: 0000000000000003
RBP: 00007f2c609f6746 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f2c60b03fa0 R15: 00007ffff1fe0778
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:tomoyo_socket_bind_permission+0xa5/0x340 security/tomoyo/network.c:727
Code: f3 f3 66 43 c7 44 2e 0e f3 f3 e8 66 2b 2d fd ba 30 00 00 00 48 89 df 31 f6 e8 67 d0 93 fd 49 8d 5c 24 18 48 89 d8 48 c1 e8 03 <42> 80 3c 28 00 74 08 48 89 df e8 7c cd 93 fd 48 8b 03 48 89 44 24
RSP: 0018:ffffc90003fd7860 EFLAGS: 00010206
RAX: 0000000000000003 RBX: 0000000000000018 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffc90003fd78d0
RBP: ffffc90003fd7950 R08: ffffc90003fd78cf R09: 0000000000000000
R10: ffffc90003fd78a0 R11: fffff520007faf1a R12: 0000000000000000
R13: dffffc0000000000 R14: 1ffff920007faf10 R15: ffff88802ef450a0
FS: 00007f2c6171f6c0(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000555567dae808 CR3: 0000000078066000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: f3 f3 66 43 c7 44 2e repz xrelease movw $0xf3f3,0xe(%r14,%r13,1)
7: 0e f3 f3
a: e8 66 2b 2d fd call 0xfd2d2b75
f: ba 30 00 00 00 mov $0x30,%edx
14: 48 89 df mov %rbx,%rdi
17: 31 f6 xor %esi,%esi
19: e8 67 d0 93 fd call 0xfd93d085
1e: 49 8d 5c 24 18 lea 0x18(%r12),%rbx
23: 48 89 d8 mov %rbx,%rax
26: 48 c1 e8 03 shr $0x3,%rax
* 2a: 42 80 3c 28 00 cmpb $0x0,(%rax,%r13,1) <-- trapping instruction
2f: 74 08 je 0x39
31: 48 89 df mov %rbx,%rdi
34: e8 7c cd 93 fd call 0xfd93cdb5
39: 48 8b 03 mov (%rbx),%rax
3c: 48 rex.W
3d: 89 .byte 0x89
3e: 44 rex.R
3f: 24 .byte 0x24


---
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 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