possible deadlock in __configfs_open_file (2)

Status: upstream: reported C repro on 2026/07/30 01:47
Subsystems: integrity lsm
Labels: prio:low
[Documentation on labels]
Reported-by: syzbot+c87014f645f2fd24312e@syzkaller.appspotmail.com
First crash: 101d, last: 17h59m
▶ ▼ ✨ AI Jobs (2)
ID Workflow Result Correct Bug Created Started Finished Revision
d715923a repro-c Reproduced: ✅ ❓ possible deadlock in __configfs_open_file (2) 2026/10/04 16:27 2026/10/04 16:27 2026/10/04 17:32 57bbd979
f325ea4d assessment-security DenialOfService: ✅ Exploitable: ❌ FilesystemTrigger: ❌ NetworkTrigger: ❌ PeripheralTrigger: ❌ RemoteTrigger: ❌ Unprivileged: ❌ UserNamespace: ❌ VMGuestTrigger: ❌ VMHostTrigger: ❌ ❓ possible deadlock in __configfs_open_file (2) 2026/07/28 01:12 2026/07/28 01:12 2026/07/28 01:56 4cb2b096
▶ ▼ Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [fs?] possible deadlock in __configfs_open_file (2) 1 (3) 2026/10/14 00:24
▶ ▼ Similar bugs (2)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 possible deadlock in __configfs_open_file origin:upstream 4 syz 2 64d 92d 0/3 upstream: reported syz repro on 2026/08/04 15:47
upstream possible deadlock in __configfs_open_file fs 4 syz, C 29 264d 682d 29/29 fixed on 2026/05/06 16:40
▶ ▼ Last patch testing requests (2)
Created Duration User Patch Repo Result
2026/10/30 01:31 12m retest repro upstream no crash job log log
2026/10/04 17:49 12m retest repro git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 6addb4f385570ebc11c4eb499a4f1c149f313e84 report job log log

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Tainted: G             L     
------------------------------------------------------
syz.7.1592/14102 is trying to acquire lock:
ffff88802bd83370 (&p->frag_sem){++++}-{4:4}, at: __configfs_open_file+0xd8/0x7d0 fs/configfs/file.c:304

but task is already holding lock:
ffff8880355d2dc8 (&ima_iint_mutex_key[depth]){+.+.}-{4:4}, at: process_measurement+0x7d0/0x1c10 security/integrity/ima/ima_main.c:319

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #3 (&ima_iint_mutex_key[depth]){+.+.}-{4:4}:
       __mutex_lock_common kernel/locking/mutex.c:646 [inline]
       __mutex_lock+0x197/0x15a0 kernel/locking/mutex.c:821
       process_measurement+0x7d0/0x1c10 security/integrity/ima/ima_main.c:319
       ima_file_check+0xdc/0x130 security/integrity/ima/ima_main.c:686
       security_file_post_open+0xb3/0x260 security/security.c:2776
       do_open fs/namei.c:4853 [inline]
       path_openat+0x1748/0x20f0 fs/namei.c:5016
       do_file_open+0x23e/0x4a0 fs/namei.c:5045
       do_sys_openat2+0x115/0x200 fs/open.c:1442
       do_sys_open fs/open.c:1448 [inline]
       __do_sys_openat fs/open.c:1464 [inline]
       __se_sys_openat fs/open.c:1459 [inline]
       __x64_sys_openat+0x138/0x170 fs/open.c:1459
       do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
       do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #2 (sb_writers#5){.+.+}-{0:0}:
       percpu_down_read_internal include/linux/percpu-rwsem.h:53 [inline]
       percpu_down_read_freezable include/linux/percpu-rwsem.h:83 [inline]
       __sb_start_write include/linux/fs/super.h:19 [inline]
       sb_start_write+0x48/0x1c0 include/linux/fs/super.h:125
       mnt_want_write+0x41/0x90 fs/namespace.c:531
       lookup_open+0x1f7/0x1ae0 fs/namei.c:4459
       open_last_lookups fs/namei.c:4774 [inline]
       path_openat+0x70c/0x20f0 fs/namei.c:5013
       do_file_open+0x23e/0x4a0 fs/namei.c:5045
       file_open_name fs/open.c:1400 [inline]
       filp_open+0x16d/0x1d0 fs/open.c:1417
       fsg_lun_open+0x6c/0xdf0 drivers/usb/gadget/function/storage_common.c:194
       fsg_store_file+0x19e/0x400 drivers/usb/gadget/function/storage_common.c:455
       flush_write_buffer fs/configfs/file.c:207 [inline]
       configfs_write_iter+0x337/0x430 fs/configfs/file.c:229
       new_sync_write fs/read_write.c:595 [inline]
       vfs_write+0x612/0xba0 fs/read_write.c:687
       ksys_write+0x150/0x270 fs/read_write.c:739
       do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
       do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #1 (&common->filesem){+.+.}-{4:4}:
       down_write+0x91/0x200 kernel/locking/rwsem.c:1631
       fsg_store_file+0x163/0x400 drivers/usb/gadget/function/storage_common.c:452
       flush_write_buffer fs/configfs/file.c:207 [inline]
       configfs_write_iter+0x337/0x430 fs/configfs/file.c:229
       new_sync_write fs/read_write.c:595 [inline]
       vfs_write+0x612/0xba0 fs/read_write.c:687
       ksys_write+0x150/0x270 fs/read_write.c:739
       do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
       do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&p->frag_sem){++++}-{4:4}:
       check_prev_add kernel/locking/lockdep.c:3209 [inline]
       check_prevs_add kernel/locking/lockdep.c:3328 [inline]
       validate_chain kernel/locking/lockdep.c:3952 [inline]
       __lock_acquire+0x164c/0x2de0 kernel/locking/lockdep.c:5288
       lock_acquire+0x115/0x350 kernel/locking/lockdep.c:5942
       down_read+0x45/0x320 kernel/locking/rwsem.c:1574
       __configfs_open_file+0xd8/0x7d0 fs/configfs/file.c:304
       do_dentry_open+0x80e/0x1360 fs/open.c:1000
       vfs_open+0x43/0x350 fs/open.c:1107
       dentry_open+0x61/0xa0 fs/open.c:1149
       ima_calc_file_hash+0x15f/0x890 security/integrity/ima/ima_crypto.c:269
       ima_collect_measurement+0x51b/0xa00 security/integrity/ima/ima_api.c:300
       process_measurement+0x1272/0x1c10 security/integrity/ima/ima_main.c:425
       ima_file_check+0xdc/0x130 security/integrity/ima/ima_main.c:686
       security_file_post_open+0xb3/0x260 security/security.c:2776
       do_open fs/namei.c:4853 [inline]
       path_openat+0x1748/0x20f0 fs/namei.c:5016
       do_file_open+0x23e/0x4a0 fs/namei.c:5045
       do_sys_openat2+0x115/0x200 fs/open.c:1442
       do_sys_open fs/open.c:1448 [inline]
       __do_sys_openat fs/open.c:1464 [inline]
       __se_sys_openat fs/open.c:1459 [inline]
       __x64_sys_openat+0x138/0x170 fs/open.c:1459
       do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
       do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

other info that might help us debug this:

Chain exists of:
  &p->frag_sem --> sb_writers#5 --> &ima_iint_mutex_key[depth]

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&ima_iint_mutex_key[depth]);
                               lock(sb_writers#5);
                               lock(&ima_iint_mutex_key[depth]);
  rlock(&p->frag_sem);

 *** DEADLOCK ***

locks held by syz.7.1592/14102: 1, last CPU#0:
 #0: ffff8880355d2dc8 (&ima_iint_mutex_key[depth]){+.+.}-{4:4}, at: process_measurement+0x7d0/0x1c10 security/integrity/ima/ima_main.c:319

stack backtrace:
CPU: 0 UID: 0 PID: 14102 Comm: syz.7.1592 Tainted: G             L      syzkaller #0 PREEMPT(full) 
Tainted: [L]=SOFTLOCKUP
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/15/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 print_circular_bug+0x2e2/0x300 kernel/locking/lockdep.c:2087
 check_noncircular+0x12f/0x150 kernel/locking/lockdep.c:2219
 check_prev_add kernel/locking/lockdep.c:3209 [inline]
 check_prevs_add kernel/locking/lockdep.c:3328 [inline]
 validate_chain kernel/locking/lockdep.c:3952 [inline]
 __lock_acquire+0x164c/0x2de0 kernel/locking/lockdep.c:5288
 lock_acquire+0x115/0x350 kernel/locking/lockdep.c:5942
 down_read+0x45/0x320 kernel/locking/rwsem.c:1574
 __configfs_open_file+0xd8/0x7d0 fs/configfs/file.c:304
 do_dentry_open+0x80e/0x1360 fs/open.c:1000
 vfs_open+0x43/0x350 fs/open.c:1107
 dentry_open+0x61/0xa0 fs/open.c:1149
 ima_calc_file_hash+0x15f/0x890 security/integrity/ima/ima_crypto.c:269
 ima_collect_measurement+0x51b/0xa00 security/integrity/ima/ima_api.c:300
 process_measurement+0x1272/0x1c10 security/integrity/ima/ima_main.c:425
 ima_file_check+0xdc/0x130 security/integrity/ima/ima_main.c:686
 security_file_post_open+0xb3/0x260 security/security.c:2776
 do_open fs/namei.c:4853 [inline]
 path_openat+0x1748/0x20f0 fs/namei.c:5016
 do_file_open+0x23e/0x4a0 fs/namei.c:5045
 do_sys_openat2+0x115/0x200 fs/open.c:1442
 do_sys_open fs/open.c:1448 [inline]
 __do_sys_openat fs/open.c:1464 [inline]
 __se_sys_openat fs/open.c:1459 [inline]
 __x64_sys_openat+0x138/0x170 fs/open.c:1459
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f4a3599fb19
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:00007f4a368f5028 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f4a35c25fa0 RCX: 00007f4a3599fb19
RDX: 0000000000000001 RSI: 0000200000001100 RDI: ffffffffffffff9c
RBP: 00007f4a35a37b70 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f4a35c26038 R14: 00007f4a35c25fa0 R15: 00007fff0503a8d8
 </TASK>

Crashes (47):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/11/04 03:56 upstream 05441d697f7f d02c3949 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in __configfs_open_file
2026/10/08 15:52 upstream 7b63ef2d55f2 4f6a9fcf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in __configfs_open_file
2026/10/08 12:09 upstream 7b63ef2d55f2 4f6a9fcf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in __configfs_open_file
2026/10/05 07:30 upstream a90ee4305c4a 57bbd979 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in __configfs_open_file
2026/10/05 01:02 upstream 6addb4f38557 57bbd979 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in __configfs_open_file
2026/09/15 01:51 upstream 704340f1cd0d 924033e8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in __configfs_open_file
2026/09/15 01:33 upstream 704340f1cd0d 924033e8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in __configfs_open_file
2026/09/15 01:33 upstream 704340f1cd0d 924033e8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in __configfs_open_file
2026/09/10 05:46 upstream 50d05c7c76c9 4e8b1cc6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in __configfs_open_file
2026/10/16 01:19 upstream 045958acaa75 3f2522c6 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __configfs_open_file
2026/10/13 22:21 git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 24a19b953e2a 4f92358f .config console log report C ci-qemu-upstream possible deadlock in __configfs_open_file
2026/10/11 07:05 upstream a5ebb76233b7 4f92358f .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __configfs_open_file
2026/10/08 15:51 upstream 0c2669a9f4a1 9d4697fa .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __configfs_open_file
2026/10/04 08:58 upstream a74306e2e676 57bbd979 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __configfs_open_file
2026/09/26 13:15 upstream f14572c203d5 a3c7249d .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __configfs_open_file
2026/09/24 21:01 upstream 5fc5768c7ca9 27d05fb3 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __configfs_open_file
2026/09/22 20:58 upstream c4e9f74da438 3e2106e5 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __configfs_open_file
2026/09/14 20:24 upstream 704340f1cd0d 924033e8 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __configfs_open_file
2026/09/10 13:54 upstream 50d05c7c76c9 1fe56c0a .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __configfs_open_file
2026/09/10 09:39 upstream 50d05c7c76c9 4e8b1cc6 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __configfs_open_file
2026/09/08 14:14 upstream 28924df2a08f 351387c4 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __configfs_open_file
2026/09/08 02:04 upstream 28924df2a08f 680aa3e1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __configfs_open_file
2026/09/02 10:01 upstream 89a312991dc6 587f6b29 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __configfs_open_file
2026/08/23 19:05 upstream 818bebeb63dd 1e72964b .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __configfs_open_file
2026/07/26 01:37 upstream 3dab139d4795 4a865b71 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __configfs_open_file
2026/10/15 15:35 upstream 0fcb05b72344 3f2522c6 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __configfs_open_file
2026/10/15 08:32 upstream 0fcb05b72344 8fb0ae89 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __configfs_open_file
2026/09/16 03:00 upstream 50d05c7c76c9 12a0a44a .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __configfs_open_file
2026/09/15 14:06 upstream 50d05c7c76c9 f41e228a .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __configfs_open_file
2026/09/15 14:06 upstream 50d05c7c76c9 f41e228a .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __configfs_open_file
2026/09/15 14:06 upstream 50d05c7c76c9 f41e228a .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __configfs_open_file
2026/09/15 09:11 upstream 50d05c7c76c9 81a27d1a .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __configfs_open_file
2026/09/14 12:57 upstream 50d05c7c76c9 924033e8 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __configfs_open_file
2026/09/14 12:57 upstream 50d05c7c76c9 924033e8 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __configfs_open_file
2026/09/14 12:57 upstream 50d05c7c76c9 924033e8 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __configfs_open_file
2026/09/13 18:48 upstream 50d05c7c76c9 70a60e12 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __configfs_open_file
2026/09/10 12:23 upstream 50d05c7c76c9 1fe56c0a .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __configfs_open_file
2026/09/10 00:45 upstream 50d05c7c76c9 4e8b1cc6 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __configfs_open_file
2026/09/10 00:45 upstream 50d05c7c76c9 4e8b1cc6 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __configfs_open_file
2026/09/10 00:44 upstream 50d05c7c76c9 4e8b1cc6 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __configfs_open_file
2026/09/06 18:04 upstream 1fc5a74b108f 4f7b22a0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __configfs_open_file
2026/09/06 04:17 upstream 9f0346dcbea3 4f7b22a0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __configfs_open_file
2026/09/06 04:16 upstream 9f0346dcbea3 4f7b22a0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __configfs_open_file
2026/10/12 22:01 linux-next 4eb2586bd40d 745a967f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in __configfs_open_file
2026/10/09 01:38 linux-next b01868671970 b2734a59 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in __configfs_open_file
2026/10/05 23:17 linux-next bf1ee2bd5c2d 1995e6c7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in __configfs_open_file
* Struck through repros no longer work on HEAD.