possible deadlock in uvcg_frame_dw_frame_interval_store

Status: upstream: reported on 2026/08/13 11:09
Subsystems: usb
Labels: prio:low
[Documentation on labels]
Reported-by: syzbot+b37b42183fe588ceeb88@syzkaller.appspotmail.com
First crash: 23d, last: 4d23h
✨ AI Jobs (5)
ID Workflow Result Correct Bug Created Started Finished Revision
d7cf7500 assessment-security DenialOfService: ✅ Exploitable: ❌ FilesystemTrigger: ❌ NetworkTrigger: ❌ PeripheralTrigger: ❌ RemoteTrigger: ❌ Unprivileged: ❌ UserNamespace: ❌ VMGuestTrigger: ❌ VMHostTrigger: ❌ possible deadlock in uvcg_frame_dw_frame_interval_store 2026/08/19 03:48 2026/08/19 03:48 2026/08/19 04:31 1e72964b
16163daf assessment-security 💥 possible deadlock in uvcg_frame_dw_frame_interval_store 2026/08/15 01:12 2026/08/15 01:12 2026/08/15 01:12 746171ee
3dd439eb repro-c Reproduced: ✅ possible deadlock in uvcg_frame_dw_frame_interval_store 2026/08/13 11:51 2026/08/13 19:07 2026/08/13 19:30 0165196a
d7660ce8 assessment-security 💥 possible deadlock in uvcg_frame_dw_frame_interval_store 2026/08/12 04:14 2026/08/12 04:14 2026/08/12 04:14 f8d35649
7d4b3dd9 assessment-security 💥 possible deadlock in uvcg_frame_dw_frame_interval_store 2026/08/11 01:43 2026/08/11 01:43 2026/08/11 01:43 039457bd
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [usb?] possible deadlock in uvcg_frame_dw_frame_interval_store 0 (1) 2026/08/13 11:09
Similar bugs (2)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 possible deadlock in uvcg_frame_dw_frame_interval_store 4 2 8d17h 14d 0/3 upstream: reported on 2026/08/17 15:39
linux-6.1 possible deadlock in uvcg_frame_dw_frame_interval_store 4 1 11d 11d 0/3 upstream: reported on 2026/08/21 11:12
Last patch testing requests (1)
Created Duration User Patch Repo Result
2026/08/13 20:02 20m nogikh@google.com upstream report job log log

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Tainted: G             L     
------------------------------------------------------
syz.2.1367/12006 is trying to acquire lock:
ffffffff903eb228 (gadget_subsys.su_mutex){+.+.}-{4:4}, at: uvcg_frame_dw_frame_interval_store+0xdf/0x4b0 drivers/usb/gadget/function/uvc_configfs.c:2076

but task is already holding lock:
ffff888075e95e70 (&p->frag_sem){++++}-{4:4}, at: flush_write_buffer fs/configfs/file.c:205 [inline]
ffff888075e95e70 (&p->frag_sem){++++}-{4:4}, at: configfs_write_iter+0x218/0x4e0 fs/configfs/file.c:229

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #3 (&p->frag_sem){++++}-{4:4}:
       lock_acquire kernel/locking/lockdep.c:5886 [inline]
       lock_acquire+0x1b9/0x370 kernel/locking/lockdep.c:5843
       down_write_killable+0x93/0x240 kernel/locking/rwsem.c:1643
       configfs_rmdir+0x3fa/0x950 fs/configfs/dir.c:1534
       vfs_rmdir fs/namei.c:5515 [inline]
       vfs_rmdir+0x328/0x8a0 fs/namei.c:5488
       filename_rmdir+0x31a/0x5c0 fs/namei.c:5572
       __do_sys_unlinkat fs/namei.c:5747 [inline]
       __se_sys_unlinkat fs/namei.c:5740 [inline]
       __x64_sys_unlinkat+0xf5/0x130 fs/namei.c:5740
       do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
       do_syscall_64+0x123/0x790 arch/x86/entry/syscall_64.c:84
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #2 (&sb->s_type->i_mutex_key#24){++++}-{4:4}:
       lock_acquire kernel/locking/lockdep.c:5886 [inline]
       lock_acquire+0x1b9/0x370 kernel/locking/lockdep.c:5843
       down_write+0x8b/0x1f0 kernel/locking/rwsem.c:1631
       inode_lock include/linux/fs.h:1025 [inline]
       configfs_depend_item_unlocked+0xf3/0x6a0 fs/configfs/dir.c:1259
       usbg_make_tpg+0x261/0x620 drivers/usb/gadget/function/f_tcm.c:1686
       target_fabric_make_tpg+0xab/0x8c0 drivers/target/target_core_fabric_configfs.c:939
       configfs_mkdir+0x51e/0xb70 fs/configfs/dir.c:1360
       vfs_mkdir+0x364/0x850 fs/namei.c:5410
       filename_mkdirat+0x48b/0x5e0 fs/namei.c:5443
       __do_sys_mkdir fs/namei.c:5470 [inline]
       __se_sys_mkdir fs/namei.c:5467 [inline]
       __x64_sys_mkdir+0x6b/0x90 fs/namei.c:5467
       do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
       do_syscall_64+0x123/0x790 arch/x86/entry/syscall_64.c:84
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #1 (&opts->dep_lock){+.+.}-{4:4}:
       lock_acquire kernel/locking/lockdep.c:5886 [inline]
       lock_acquire+0x1b9/0x370 kernel/locking/lockdep.c:5843
       __mutex_lock_common kernel/locking/mutex.c:646 [inline]
       __mutex_lock+0x1a4/0x1bc0 kernel/locking/mutex.c:821
       tcm_set_name+0x29/0xb0 drivers/usb/gadget/function/f_tcm.c:2669
       function_make+0x21c/0x3f0 drivers/usb/gadget/configfs.c:636
       configfs_mkdir+0x51e/0xb70 fs/configfs/dir.c:1360
       vfs_mkdir+0x364/0x850 fs/namei.c:5410
       filename_mkdirat+0x48b/0x5e0 fs/namei.c:5443
       __do_sys_mkdir fs/namei.c:5470 [inline]
       __se_sys_mkdir fs/namei.c:5467 [inline]
       __x64_sys_mkdir+0x6b/0x90 fs/namei.c:5467
       do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
       do_syscall_64+0x123/0x790 arch/x86/entry/syscall_64.c:84
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (gadget_subsys.su_mutex){+.+.}-{4:4}:
       check_prev_add+0xeb/0xe60 kernel/locking/lockdep.c:3181
       check_prevs_add kernel/locking/lockdep.c:3300 [inline]
       validate_chain kernel/locking/lockdep.c:3924 [inline]
       __lock_acquire+0x1492/0x1ec0 kernel/locking/lockdep.c:5253
       lock_acquire kernel/locking/lockdep.c:5886 [inline]
       lock_acquire+0x1b9/0x370 kernel/locking/lockdep.c:5843
       __mutex_lock_common kernel/locking/mutex.c:646 [inline]
       __mutex_lock+0x1a4/0x1bc0 kernel/locking/mutex.c:821
       uvcg_frame_dw_frame_interval_store+0xdf/0x4b0 drivers/usb/gadget/function/uvc_configfs.c:2076
       flush_write_buffer fs/configfs/file.c:207 [inline]
       configfs_write_iter+0x302/0x4e0 fs/configfs/file.c:229
       new_sync_write fs/read_write.c:595 [inline]
       vfs_write+0x6af/0x1050 fs/read_write.c:687
       ksys_write+0x12a/0x250 fs/read_write.c:739
       do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
       do_syscall_64+0x123/0x790 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:
  gadget_subsys.su_mutex --> &sb->s_type->i_mutex_key#24 --> &p->frag_sem

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  rlock(&p->frag_sem);
                               lock(&sb->s_type->i_mutex_key#24);
                               lock(&p->frag_sem);
  lock(gadget_subsys.su_mutex);

 *** DEADLOCK ***

locks held by syz.2.1367/12006: 4, last CPU#1:
 #0: ffff88803770c2b0 (&f->f_pos_lock){+.+.}-{4:4}, at: fdget_pos+0x2aa/0x380 fs/file.c:1259
 #1: ffff88801eb4c460 (sb_writers#13){.+.+}-{0:0}, at: ksys_write+0x12a/0x250 fs/read_write.c:739
 #2: ffff888027967280 (&buffer->mutex){+.+.}-{4:4}, at: configfs_write_iter+0x76/0x4e0 fs/configfs/file.c:226
 #3: ffff888075e95e70 (&p->frag_sem){++++}-{4:4}, at: flush_write_buffer fs/configfs/file.c:205 [inline]
 #3: ffff888075e95e70 (&p->frag_sem){++++}-{4:4}, at: configfs_write_iter+0x218/0x4e0 fs/configfs/file.c:229

stack backtrace:
CPU: 1 UID: 0 PID: 12006 Comm: syz.2.1367 Tainted: G             L      syzkaller #0 PREEMPT(full) 
Tainted: [L]=SOFTLOCKUP
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/05/2026
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x100/0x190 lib/dump_stack.c:120
 print_circular_bug.cold+0x178/0x1be kernel/locking/lockdep.c:2059
 check_noncircular+0x146/0x160 kernel/locking/lockdep.c:2191
 check_prev_add+0xeb/0xe60 kernel/locking/lockdep.c:3181
 check_prevs_add kernel/locking/lockdep.c:3300 [inline]
 validate_chain kernel/locking/lockdep.c:3924 [inline]
 __lock_acquire+0x1492/0x1ec0 kernel/locking/lockdep.c:5253
 lock_acquire kernel/locking/lockdep.c:5886 [inline]
 lock_acquire+0x1b9/0x370 kernel/locking/lockdep.c:5843
 __mutex_lock_common kernel/locking/mutex.c:646 [inline]
 __mutex_lock+0x1a4/0x1bc0 kernel/locking/mutex.c:821
 uvcg_frame_dw_frame_interval_store+0xdf/0x4b0 drivers/usb/gadget/function/uvc_configfs.c:2076
 flush_write_buffer fs/configfs/file.c:207 [inline]
 configfs_write_iter+0x302/0x4e0 fs/configfs/file.c:229
 new_sync_write fs/read_write.c:595 [inline]
 vfs_write+0x6af/0x1050 fs/read_write.c:687
 ksys_write+0x12a/0x250 fs/read_write.c:739
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x123/0x790 arch/x86/entry/syscall_64.c:84
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f38b2b9e0d9
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:00007f38b3b4b028 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f38b2e25fa0 RCX: 00007f38b2b9e0d9
RDX: 0000000000000007 RSI: 0000200000000540 RDI: 0000000000000006
RBP: 00007f38b2c35024 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f38b2e26038 R14: 00007f38b2e25fa0 R15: 00007ffd353b36f8
 </TASK>

Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/08/22 23:49 upstream 66fb95a52111 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in uvcg_frame_dw_frame_interval_store
2026/08/16 11:02 upstream 3eb40771c00a 746171ee .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in uvcg_frame_dw_frame_interval_store
2026/08/27 12:47 upstream 818bebeb63dd c53a1b9c .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in uvcg_frame_dw_frame_interval_store
2026/08/09 11:02 upstream 06cf61899d64 5d63f80b .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in uvcg_frame_dw_frame_interval_store
* Struck through repros no longer work on HEAD.