[moderation] [selinux?] general protection fault in __inode_security_revalidate

1 view
Skip to first unread message

syzbot

unread,
May 6, 2024, 10:22:25 PMMay 6
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 49a73b1652c5 Merge tag 'firewire-fixes-6.9-rc6' of git://g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17347554980000
kernel config: https://syzkaller.appspot.com/x/.config?x=3310e643b6ef5d69
dashboard link: https://syzkaller.appspot.com/bug?extid=64008256791f87511b21
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
CC: [linux-...@vger.kernel.org omos...@redhat.com pa...@paul-moore.com sel...@vger.kernel.org stephen.sm...@gmail.com]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/62800dc73251/disk-49a73b16.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/231b3cdc2f46/vmlinux-49a73b16.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cbc5d05e7e01/bzImage-49a73b16.xz

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

ERROR: (device loop4): jfs_readdir: JFS:Dtree error: ino = 2, bn=0, index = 5
ERROR: (device loop4): jfs_readdir: JFS:Dtree error: ino = 2, bn=0, index = 6
general protection fault, probably for non-canonical address 0xdffffc018c2c0715: 0000 [#1] PREEMPT SMP KASAN PTI
KASAN: probably user-memory-access in range [0x0000000c616038a8-0x0000000c616038af]
CPU: 0 PID: 18260 Comm: syz-executor.4 Not tainted 6.9.0-rc6-syzkaller-00113-g49a73b1652c5 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:__inode_security_revalidate+0xb1/0x1b0 security/selinux/hooks.c:286
Code: 89 d8 5b 5d 41 5c 41 5d 41 5e c3 cc cc cc cc e8 25 05 55 fd 49 8d 7c 24 22 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 <0f> b6 04 02 48 89 fa 83 e2 07 38 d0 7f 08 84 c0 0f 85 c3 00 00 00
RSP: 0018:ffffc9000332f9e0 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: 0000000000000001 RCX: ffffffff8438c0ec
RDX: 000000018c2c0715 RSI: ffffffff8438c10b RDI: 0000000c616038aa
RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000001 R12: 0000000c61603888
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000080
FS: 000055556e394480(0000) GS:ffff8880b9400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffc030fec18 CR3: 000000002344c000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inode_security_rcu security/selinux/hooks.c:309 [inline]
selinux_inode_permission+0x297/0x5c0 security/selinux/hooks.c:3120
security_inode_permission+0xbb/0x120 security/security.c:2216
inode_permission fs/namei.c:536 [inline]
inode_permission+0x17a/0x5f0 fs/namei.c:503
may_lookup fs/namei.c:1718 [inline]
link_path_walk.part.0.constprop.0+0x226/0xcd0 fs/namei.c:2273
link_path_walk fs/namei.c:2255 [inline]
path_lookupat+0x93/0x770 fs/namei.c:2484
filename_lookup+0x1e5/0x5b0 fs/namei.c:2514
user_path_at_empty+0x42/0x60 fs/namei.c:2921
user_path_at include/linux/namei.h:57 [inline]
ksys_umount fs/namespace.c:1916 [inline]
__do_sys_umount fs/namespace.c:1924 [inline]
__se_sys_umount fs/namespace.c:1922 [inline]
__x64_sys_umount+0x10e/0x1a0 fs/namespace.c:1922
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcf/0x260 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fe91887f057
Code: b0 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 b0 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007ffc030ff3c8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: ffffffffffffffda RBX: 00007fe9188c93b9 RCX: 00007fe91887f057
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffc030ff480
RBP: 00007ffc030ff480 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007ffc03100570
R13: 00007fe9188c93b9 R14: 00007fe9188dd6b8 R15: 0000000000000015
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__inode_security_revalidate+0xb1/0x1b0 security/selinux/hooks.c:286
Code: 89 d8 5b 5d 41 5c 41 5d 41 5e c3 cc cc cc cc e8 25 05 55 fd 49 8d 7c 24 22 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 <0f> b6 04 02 48 89 fa 83 e2 07 38 d0 7f 08 84 c0 0f 85 c3 00 00 00
RSP: 0018:ffffc9000332f9e0 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: 0000000000000001 RCX: ffffffff8438c0ec
RDX: 000000018c2c0715 RSI: ffffffff8438c10b RDI: 0000000c616038aa
RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000001 R12: 0000000c61603888
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000080
FS: 000055556e394480(0000) GS:ffff8880b9400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b31f2e000 CR3: 000000002344c000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 89 d8 mov %ebx,%eax
2: 5b pop %rbx
3: 5d pop %rbp
4: 41 5c pop %r12
6: 41 5d pop %r13
8: 41 5e pop %r14
a: c3 ret
b: cc int3
c: cc int3
d: cc int3
e: cc int3
f: e8 25 05 55 fd call 0xfd550539
14: 49 8d 7c 24 22 lea 0x22(%r12),%rdi
19: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
20: fc ff df
23: 48 89 fa mov %rdi,%rdx
26: 48 c1 ea 03 shr $0x3,%rdx
* 2a: 0f b6 04 02 movzbl (%rdx,%rax,1),%eax <-- trapping instruction
2e: 48 89 fa mov %rdi,%rdx
31: 83 e2 07 and $0x7,%edx
34: 38 d0 cmp %dl,%al
36: 7f 08 jg 0x40
38: 84 c0 test %al,%al
3a: 0f 85 c3 00 00 00 jne 0x103


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