possible deadlock in uvcg_frame_dw_max_video_frame_buffer_size_store

Status: upstream: reported on 2026/08/26 17:51
Reported-by: syzbot+3c069fb69a0a6e00630b@syzkaller.appspotmail.com
First crash: 2d16h, last: 2d16h
Similar bugs (2)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.6 possible deadlock in uvcg_frame_dw_max_video_frame_buffer_size_store 4 2 4d05h 4d05h 0/2 upstream: reported on 2026/08/25 04:30
upstream possible deadlock in uvcg_frame_dw_max_video_frame_buffer_size_store fs prio:low 4 16 5d20h 9d20h 0/29 upstream: reported on 2026/08/19 13:59

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.0.2004/13514 is trying to acquire lock:
ffffffff8d7b3730 (gadget_subsys.su_mutex){+.+.}-{3:3}, at: uvcg_frame_dw_max_video_frame_buffer_size_store+0x111/0x360 drivers/usb/gadget/function/uvc_configfs.c:1160

but task is already holding lock:
ffff88814d3b1778 (&p->frag_sem){++++}-{3:3}, at: flush_write_buffer fs/configfs/file.c:205 [inline]
ffff88814d3b1778 (&p->frag_sem){++++}-{3:3}, at: configfs_write_iter+0x20e/0x400 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){++++}-{3:3}:
       down_write_killable+0x45/0x90 kernel/locking/rwsem.c:1584
       configfs_rmdir+0x3e0/0x980 fs/configfs/dir.c:1534
       vfs_rmdir+0x34e/0x4a0 fs/namei.c:4242
       do_rmdir+0x29a/0x5c0 fs/namei.c:4303
       __do_sys_unlinkat fs/namei.c:4483 [inline]
       __se_sys_unlinkat fs/namei.c:4477 [inline]
       __x64_sys_unlinkat+0xc0/0xe0 fs/namei.c:4477
       do_syscall_x64 arch/x86/entry/common.c:46 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #2 (&sb->s_type->i_mutex_key#23){++++}-{3:3}:
       down_write+0x36/0x60 kernel/locking/rwsem.c:1573
       inode_lock include/linux/fs.h:764 [inline]
       configfs_depend_item_unlocked+0x14f/0x430 fs/configfs/dir.c:1255
       usbg_make_tpg+0x1f3/0x580 drivers/usb/gadget/function/f_tcm.c:1365
       target_fabric_make_tpg+0xa0/0x6d0 drivers/target/target_core_fabric_configfs.c:905
       configfs_mkdir+0x511/0x9e0 fs/configfs/dir.c:1360
       vfs_mkdir+0x386/0x570 fs/namei.c:4157
       do_mkdirat+0x1d8/0x440 fs/namei.c:4182
       __do_sys_mkdir fs/namei.c:4202 [inline]
       __se_sys_mkdir fs/namei.c:4200 [inline]
       __x64_sys_mkdir+0x6a/0x80 fs/namei.c:4200
       do_syscall_x64 arch/x86/entry/common.c:46 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #1 (&opts->dep_lock){+.+.}-{3:3}:
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x12d/0xae0 kernel/locking/mutex.c:747
       tcm_set_name+0x26/0x90 drivers/usb/gadget/function/f_tcm.c:2348
       function_make+0x195/0x350 drivers/usb/gadget/configfs.c:625
       configfs_mkdir+0x511/0x9e0 fs/configfs/dir.c:1360
       vfs_mkdir+0x386/0x570 fs/namei.c:4157
       do_mkdirat+0x1d8/0x440 fs/namei.c:4182
       __do_sys_mkdir fs/namei.c:4202 [inline]
       __se_sys_mkdir fs/namei.c:4200 [inline]
       __x64_sys_mkdir+0x6a/0x80 fs/namei.c:4200
       do_syscall_x64 arch/x86/entry/common.c:46 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #0 (gadget_subsys.su_mutex){+.+.}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3095 [inline]
       check_prevs_add kernel/locking/lockdep.c:3214 [inline]
       validate_chain kernel/locking/lockdep.c:3830 [inline]
       __lock_acquire+0x2d18/0x7c40 kernel/locking/lockdep.c:5063
       lock_acquire+0x1bb/0x4a0 kernel/locking/lockdep.c:5676
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x12d/0xae0 kernel/locking/mutex.c:747
       uvcg_frame_dw_max_video_frame_buffer_size_store+0x111/0x360 drivers/usb/gadget/function/uvc_configfs.c:1160
       flush_write_buffer fs/configfs/file.c:207 [inline]
       configfs_write_iter+0x30b/0x400 fs/configfs/file.c:229
       call_write_iter include/linux/fs.h:2271 [inline]
       new_sync_write fs/read_write.c:491 [inline]
       vfs_write+0x482/0x9a0 fs/read_write.c:584
       ksys_write+0x14d/0x260 fs/read_write.c:637
       do_syscall_x64 arch/x86/entry/common.c:46 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

other info that might help us debug this:

Chain exists of:
  gadget_subsys.su_mutex --> &sb->s_type->i_mutex_key#23 --> &p->frag_sem

 Possible unsafe locking scenario:

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

 *** DEADLOCK ***

4 locks held by syz.0.2004/13514:
 #0: ffff88807f7e5268 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x2ae/0x360 fs/file.c:1038
 #1: ffff888148ac2460 (sb_writers#14){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
 #2: ffff88802ed4d288 (&buffer->mutex){+.+.}-{3:3}, at: configfs_write_iter+0x7d/0x400 fs/configfs/file.c:226
 #3: ffff88814d3b1778 (&p->frag_sem){++++}-{3:3}, at: flush_write_buffer fs/configfs/file.c:205 [inline]
 #3: ffff88814d3b1778 (&p->frag_sem){++++}-{3:3}, at: configfs_write_iter+0x20e/0x400 fs/configfs/file.c:229

stack backtrace:
CPU: 0 PID: 13514 Comm: syz.0.2004 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0x188/0x24e lib/dump_stack.c:106
 check_noncircular+0x296/0x330 kernel/locking/lockdep.c:2170
 check_prev_add kernel/locking/lockdep.c:3095 [inline]
 check_prevs_add kernel/locking/lockdep.c:3214 [inline]
 validate_chain kernel/locking/lockdep.c:3830 [inline]
 __lock_acquire+0x2d18/0x7c40 kernel/locking/lockdep.c:5063
 lock_acquire+0x1bb/0x4a0 kernel/locking/lockdep.c:5676
 __mutex_lock_common kernel/locking/mutex.c:603 [inline]
 __mutex_lock+0x12d/0xae0 kernel/locking/mutex.c:747
 uvcg_frame_dw_max_video_frame_buffer_size_store+0x111/0x360 drivers/usb/gadget/function/uvc_configfs.c:1160
 flush_write_buffer fs/configfs/file.c:207 [inline]
 configfs_write_iter+0x30b/0x400 fs/configfs/file.c:229
 call_write_iter include/linux/fs.h:2271 [inline]
 new_sync_write fs/read_write.c:491 [inline]
 vfs_write+0x482/0x9a0 fs/read_write.c:584
 ksys_write+0x14d/0x260 fs/read_write.c:637
 do_syscall_x64 arch/x86/entry/common.c:46 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f320fb9e0d9
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:00007f3210af7028 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f320fe26090 RCX: 00007f320fb9e0d9
RDX: 0000000000000004 RSI: 00002000000006c0 RDI: 0000000000000008
RBP: 00007f320fc35024 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f320fe26128 R14: 00007f320fe26090 R15: 00007ffc048047b8
 </TASK>

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/08/26 17:51 linux-6.1.y 05208478041c a2b77b9e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in uvcg_frame_dw_max_video_frame_buffer_size_store
* Struck through repros no longer work on HEAD.