linux-kernel - [syzbot] [tomoyo?] general protection fault in tomoyo_get

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <67812ce5.050a0220.d0267.002e.GAE@google.com>
Date: Fri, 10 Jan 2025 06:21:25 -0800
From: syzbot <syzbot+298f8ae1e0bde70f8e0d@...kaller.appspotmail.com>
To: jmorris@...ei.org, linux-kernel@...r.kernel.org, 
	linux-security-module@...r.kernel.org, paul@...l-moore.com, 
	penguin-kernel@...ove.SAKURA.ne.jp, serge@...lyn.com, 
	syzkaller-bugs@...glegroups.com, takedakn@...data.co.jp, 
	tomoyo-dev-en@...ts.osdn.me
Subject: [syzbot] [tomoyo?] general protection fault in tomoyo_get_name (2)

Hello,

syzbot found the following issue on:

HEAD commit:    fc033cf25e61 Linux 6.13-rc5
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14146af8580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=86dd15278dbfe19f
dashboard link: https://syzkaller.appspot.com/bug?extid=298f8ae1e0bde70f8e0d
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/667548f224c3/disk-fc033cf2.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/66b97f5d4785/vmlinux-fc033cf2.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b27868bf31d2/bzImage-fc033cf2.xz

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

Oops: general protection fault, probably for non-canonical address 0xdffffc0000000004: 0000 [#1] PREEMPT SMP KASAN PTI
KASAN: null-ptr-deref in range [0x0000000000000020-0x0000000000000027]
CPU: 1 UID: 0 PID: 20911 Comm: getty Not tainted 6.13.0-rc5-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:tomoyo_get_name+0xed/0x490 security/tomoyo/memory.c:167
Code: 48 8b 98 40 af 51 9a 48 39 dd 0f 84 53 01 00 00 49 bd 00 00 00 00 00 fc ff df e8 de 2c 47 fd 48 8d 7b 20 48 89 f8 48 c1 e8 03 <42> 0f b6 04 28 84 c0 74 08 3c 03 0f 8e 00 03 00 00 44 8b 7b 20 44
RSP: 0018:ffffc9000c44f2d0 EFLAGS: 00010202
RAX: 0000000000000004 RBX: 0000000000000000 RCX: ffffffff8452230d
RDX: ffff888064da9e00 RSI: ffffffff845222e2 RDI: 0000000000000020
RBP: ffffffff9a51afa0 R08: 0000000000000004 R09: 0000000000000000
R10: 000000008332dfba R11: 0000000000000001 R12: 000000008332dfba
R13: dffffc0000000000 R14: ffff888029ad8d0a R15: 0000000000000000
FS:  00007f89fe493380(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000561fe8218cc8 CR3: 0000000030f66000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 tomoyo_parse_name_union+0x121/0x1f0 security/tomoyo/util.c:260
 tomoyo_update_path_acl security/tomoyo/file.c:395 [inline]
 tomoyo_write_file+0x4d3/0x7f0 security/tomoyo/file.c:1022
 tomoyo_write_domain2+0x129/0x1f0 security/tomoyo/common.c:1144
 tomoyo_add_entry security/tomoyo/common.c:2034 [inline]
 tomoyo_supervisor+0x4ad/0x1180 security/tomoyo/common.c:2095
 tomoyo_audit_path_log security/tomoyo/file.c:168 [inline]
 tomoyo_path_permission security/tomoyo/file.c:587 [inline]
 tomoyo_path_permission+0x270/0x3b0 security/tomoyo/file.c:573
 tomoyo_check_open_permission+0x37d/0x3c0 security/tomoyo/file.c:777
 tomoyo_file_open+0x6b/0x90 security/tomoyo/tomoyo.c:334
 security_file_open+0x84/0x1e0 security/security.c:3105
 do_dentry_open+0x57e/0x1ea0 fs/open.c:928
 vfs_open+0x82/0x3f0 fs/open.c:1075
 do_open fs/namei.c:3828 [inline]
 path_openat+0x1e6a/0x2d60 fs/namei.c:3987
 do_filp_open+0x20c/0x470 fs/namei.c:4014
 do_sys_openat2+0x17a/0x1e0 fs/open.c:1402
 do_sys_open fs/open.c:1417 [inline]
 __do_sys_openat fs/open.c:1433 [inline]
 __se_sys_openat fs/open.c:1428 [inline]
 __x64_sys_openat+0x175/0x210 fs/open.c:1428
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f89fe5e79a4
Code: 24 20 48 8d 44 24 30 48 89 44 24 28 64 8b 04 25 18 00 00 00 85 c0 75 2c 44 89 e2 48 89 ee bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 76 60 48 8b 15 55 a4 0d 00 f7 d8 64 89 02 48 83
RSP: 002b:00007fff57111b40 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 0000000000000008 RCX: 00007f89fe5e79a4
RDX: 0000000000000000 RSI: 00007f89fe77bf2c RDI: 00000000ffffff9c
RBP: 00007f89fe77bf2c R08: 0000000000000008 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f89fe78d513 R14: 0000000000000001 R15: 0000000000000002
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:tomoyo_get_name+0xed/0x490 security/tomoyo/memory.c:167
Code: 48 8b 98 40 af 51 9a 48 39 dd 0f 84 53 01 00 00 49 bd 00 00 00 00 00 fc ff df e8 de 2c 47 fd 48 8d 7b 20 48 89 f8 48 c1 e8 03 <42> 0f b6 04 28 84 c0 74 08 3c 03 0f 8e 00 03 00 00 44 8b 7b 20 44
RSP: 0018:ffffc9000c44f2d0 EFLAGS: 00010202
RAX: 0000000000000004 RBX: 0000000000000000 RCX: ffffffff8452230d
RDX: ffff888064da9e00 RSI: ffffffff845222e2 RDI: 0000000000000020
RBP: ffffffff9a51afa0 R08: 0000000000000004 R09: 0000000000000000
R10: 000000008332dfba R11: 0000000000000001 R12: 000000008332dfba
R13: dffffc0000000000 R14: ffff888029ad8d0a R15: 0000000000000000
FS:  00007f89fe493380(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b30d0dff8 CR3: 0000000030f66000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
   0:	48 8b 98 40 af 51 9a 	mov    -0x65ae50c0(%rax),%rbx
   7:	48 39 dd             	cmp    %rbx,%rbp
   a:	0f 84 53 01 00 00    	je     0x163
  10:	49 bd 00 00 00 00 00 	movabs $0xdffffc0000000000,%r13
  17:	fc ff df
  1a:	e8 de 2c 47 fd       	call   0xfd472cfd
  1f:	48 8d 7b 20          	lea    0x20(%rbx),%rdi
  23:	48 89 f8             	mov    %rdi,%rax
  26:	48 c1 e8 03          	shr    $0x3,%rax
* 2a:	42 0f b6 04 28       	movzbl (%rax,%r13,1),%eax <-- trapping instruction
  2f:	84 c0                	test   %al,%al
  31:	74 08                	je     0x3b
  33:	3c 03                	cmp    $0x3,%al
  35:	0f 8e 00 03 00 00    	jle    0x33b
  3b:	44 8b 7b 20          	mov    0x20(%rbx),%r15d
  3f:	44                   	rex.R


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