possible deadlock in process_measurement (2)

Status: upstream: reported C repro on 2026/08/04 15:46
Reported-by: syzbot+8af2a339711decf34817@syzkaller.appspotmail.com
First crash: 51d, last: 1d08h
▶ ▼ Bug presence (1)
Date Name Commit Repro Result
2026/08/28 upstream (ToT) 1b78070aaef6 C Failed due to an error; will retry later
▶ ▼ Similar bugs (10)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in process_measurement (5) integrity lsm 4 49 361d 497d 0/29 auto-obsoleted due to no activity on 2025/12/07 20:43
linux-6.6 possible deadlock in process_measurement 4 12 8d06h 46d 0/2 upstream: reported on 2026/08/10 07:52
upstream possible deadlock in process_measurement (4) integrity lsm 4 syz, C done 7976 690d 727d 28/29 fixed on 2024/11/14 10:09
upstream possible deadlock in process_measurement (2) integrity lsm 4 syz, C done done 56 2121d 2488d 15/29 fixed on 2021/01/06 01:14
upstream possible deadlock in process_measurement (3) overlayfs 4 syz, C error 223 1057d 1963d 0/29 closed as dup on 2023/06/06 09:59
upstream possible deadlock in process_measurement (6) prio:low ext4 4 syz, C 1126 2h35m 57d 23/29 upstream: reported C repro on 2026/07/30 00:19
linux-4.19 possible deadlock in process_measurement 4 156 1472d 2444d 0/1 auto-obsoleted due to no activity on 2023/01/11 22:20
upstream possible deadlock in process_measurement integrity lsm 4 syz, C 51 2669d 2901d 0/29 closed as invalid on 2019/07/15 16:35
linux-6.1 possible deadlock in process_measurement origin:lts-only 4 syz, C unreliable 4422 1d01h 1119d 0/3 upstream: reported C repro on 2023/09/02 00:54
linux-5.15 possible deadlock in process_measurement origin:lts-only 4 syz, C done 4 1041d 1117d 0/3 auto-obsoleted due to no activity on 2024/10/03 14:31
▶ ▼ Last patch testing requests (2)
Created Duration User Patch Repo Result
2026/09/22 14:10 11m retest repro linux-5.15.y report job log log
2026/09/22 14:10 16m retest repro linux-5.15.y report job log log

Sample crash report:
ext4 filesystem being mounted at /0/file0aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa supports timestamps until 2038-01-19 (0x7fffffff)
Mass Storage Function, version: 2009/09/11
LUN: removable file: (no medium)
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.0.17/4316 is trying to acquire lock:
ffff88807c45f520 (&iint_mutex_key[depth]){+.+.}-{3:3}, at: process_measurement+0x724/0x1c20 security/integrity/ima/ima_main.c:261

but task is already holding lock:
ffff88807c236128 (&common->filesem){++++}-{3:3}, at: fsg_store_file+0x174/0x530 drivers/usb/gadget/function/storage_common.c:451

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #3 (&common->filesem){++++}-{3:3}:
       down_read+0x44/0x2e0 kernel/locking/rwsem.c:1498
       fsg_show_file+0x29/0x130 drivers/usb/gadget/function/storage_common.c:338
       fill_read_buffer fs/configfs/file.c:68 [inline]
       configfs_read_iter+0x296/0x560 fs/configfs/file.c:88
       __kernel_read+0x51d/0x980 fs/read_write.c:443
       integrity_kernel_read+0x86/0xd0 security/integrity/iint.c:228
       ima_calc_file_hash_tfm security/integrity/ima/ima_crypto.c:485 [inline]
       ima_calc_file_shash security/integrity/ima/ima_crypto.c:516 [inline]
       ima_calc_file_hash+0x946/0x1940 security/integrity/ima/ima_crypto.c:573
       ima_collect_measurement+0x335/0x7e0 security/integrity/ima/ima_api.c:255
       process_measurement+0x1185/0x1c20 security/integrity/ima/ima_main.c:351
       ima_file_check+0xc7/0x110 security/integrity/ima/ima_main.c:533
       do_open fs/namei.c:3618 [inline]
       path_openat+0x27cf/0x2fb0 fs/namei.c:3750
       do_filp_open+0x1df/0x400 fs/namei.c:3777
       do_sys_openat2+0x14b/0x500 fs/open.c:1255
       do_sys_open fs/open.c:1271 [inline]
       __do_sys_openat fs/open.c:1287 [inline]
       __se_sys_openat fs/open.c:1282 [inline]
       __x64_sys_openat+0x135/0x160 fs/open.c:1282
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

-> #2 (&p->frag_sem){.+.+}-{3:3}:
       down_read+0x44/0x2e0 kernel/locking/rwsem.c:1498
       fill_read_buffer fs/configfs/file.c:66 [inline]
       configfs_read_iter+0x19e/0x560 fs/configfs/file.c:88
       __kernel_read+0x51d/0x980 fs/read_write.c:443
       integrity_kernel_read+0x86/0xd0 security/integrity/iint.c:228
       ima_calc_file_hash_tfm security/integrity/ima/ima_crypto.c:485 [inline]
       ima_calc_file_shash security/integrity/ima/ima_crypto.c:516 [inline]
       ima_calc_file_hash+0x946/0x1940 security/integrity/ima/ima_crypto.c:573
       ima_collect_measurement+0x335/0x7e0 security/integrity/ima/ima_api.c:255
       process_measurement+0x1185/0x1c20 security/integrity/ima/ima_main.c:351
       ima_file_check+0xc7/0x110 security/integrity/ima/ima_main.c:533
       do_open fs/namei.c:3618 [inline]
       path_openat+0x27cf/0x2fb0 fs/namei.c:3750
       do_filp_open+0x1df/0x400 fs/namei.c:3777
       do_sys_openat2+0x14b/0x500 fs/open.c:1255
       do_sys_open fs/open.c:1271 [inline]
       __do_sys_openat fs/open.c:1287 [inline]
       __se_sys_openat fs/open.c:1282 [inline]
       __x64_sys_openat+0x135/0x160 fs/open.c:1282
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

-> #1 (&buffer->mutex){+.+.}-{3:3}:
       __mutex_lock_common+0x1e5/0x2400 kernel/locking/mutex.c:596
       __mutex_lock kernel/locking/mutex.c:729 [inline]
       mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
       configfs_read_iter+0x6e/0x560 fs/configfs/file.c:86
       __kernel_read+0x51d/0x980 fs/read_write.c:443
       integrity_kernel_read+0x86/0xd0 security/integrity/iint.c:228
       ima_calc_file_hash_tfm security/integrity/ima/ima_crypto.c:485 [inline]
       ima_calc_file_shash security/integrity/ima/ima_crypto.c:516 [inline]
       ima_calc_file_hash+0x946/0x1940 security/integrity/ima/ima_crypto.c:573
       ima_collect_measurement+0x335/0x7e0 security/integrity/ima/ima_api.c:255
       process_measurement+0x1185/0x1c20 security/integrity/ima/ima_main.c:351
       ima_file_check+0xc7/0x110 security/integrity/ima/ima_main.c:533
       do_open fs/namei.c:3618 [inline]
       path_openat+0x27cf/0x2fb0 fs/namei.c:3750
       do_filp_open+0x1df/0x400 fs/namei.c:3777
       do_sys_openat2+0x14b/0x500 fs/open.c:1255
       do_sys_open fs/open.c:1271 [inline]
       __do_sys_openat fs/open.c:1287 [inline]
       __se_sys_openat fs/open.c:1282 [inline]
       __x64_sys_openat+0x135/0x160 fs/open.c:1282
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

-> #0 (&iint_mutex_key[depth]){+.+.}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3053 [inline]
       check_prevs_add kernel/locking/lockdep.c:3172 [inline]
       validate_chain kernel/locking/lockdep.c:3788 [inline]
       __lock_acquire+0x2c66/0x7b50 kernel/locking/lockdep.c:5012
       lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623
       __mutex_lock_common+0x1e5/0x2400 kernel/locking/mutex.c:596
       __mutex_lock kernel/locking/mutex.c:729 [inline]
       mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
       process_measurement+0x724/0x1c20 security/integrity/ima/ima_main.c:261
       ima_file_check+0xc7/0x110 security/integrity/ima/ima_main.c:533
       do_open fs/namei.c:3618 [inline]
       path_openat+0x27cf/0x2fb0 fs/namei.c:3750
       do_filp_open+0x1df/0x400 fs/namei.c:3777
       file_open_name fs/open.c:1200 [inline]
       filp_open+0x17c/0x1e0 fs/open.c:1220
       fsg_lun_open+0x63/0xee0 drivers/usb/gadget/function/storage_common.c:193
       fsg_store_file+0x1a5/0x530 drivers/usb/gadget/function/storage_common.c:454
       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:2173 [inline]
       new_sync_write fs/read_write.c:507 [inline]
       vfs_write+0x748/0xd70 fs/read_write.c:594
       ksys_write+0x153/0x260 fs/read_write.c:647
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

other info that might help us debug this:

Chain exists of:
  &iint_mutex_key[depth] --> &p->frag_sem --> &common->filesem

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&common->filesem);
                               lock(&p->frag_sem);
                               lock(&common->filesem);
  lock(&iint_mutex_key[depth]);

 *** DEADLOCK ***

4 locks held by syz.0.17/4316:
 #0: ffff88801dc28460 (sb_writers#13){.+.+}-{0:0}, at: vfs_write+0x296/0xd70 fs/read_write.c:590
 #1: ffff888077f5e288 (&buffer->mutex){+.+.}-{3:3}, at: configfs_write_iter+0x7d/0x400 fs/configfs/file.c:226
 #2: ffff8881435e2e78 (&p->frag_sem){.+.+}-{3:3}, at: flush_write_buffer fs/configfs/file.c:205 [inline]
 #2: ffff8881435e2e78 (&p->frag_sem){.+.+}-{3:3}, at: configfs_write_iter+0x20e/0x400 fs/configfs/file.c:229
 #3: ffff88807c236128 (&common->filesem){++++}-{3:3}, at: fsg_store_file+0x174/0x530 drivers/usb/gadget/function/storage_common.c:451

stack backtrace:
CPU: 1 PID: 4316 Comm: syz.0.17 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/0x250 lib/dump_stack.c:106
 check_noncircular+0x296/0x330 kernel/locking/lockdep.c:2133
 check_prev_add kernel/locking/lockdep.c:3053 [inline]
 check_prevs_add kernel/locking/lockdep.c:3172 [inline]
 validate_chain kernel/locking/lockdep.c:3788 [inline]
 __lock_acquire+0x2c66/0x7b50 kernel/locking/lockdep.c:5012
 lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623
 __mutex_lock_common+0x1e5/0x2400 kernel/locking/mutex.c:596
 __mutex_lock kernel/locking/mutex.c:729 [inline]
 mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
 process_measurement+0x724/0x1c20 security/integrity/ima/ima_main.c:261
 ima_file_check+0xc7/0x110 security/integrity/ima/ima_main.c:533
 do_open fs/namei.c:3618 [inline]
 path_openat+0x27cf/0x2fb0 fs/namei.c:3750
 do_filp_open+0x1df/0x400 fs/namei.c:3777
 file_open_name fs/open.c:1200 [inline]
 filp_open+0x17c/0x1e0 fs/open.c:1220
 fsg_lun_open+0x63/0xee0 drivers/usb/gadget/function/storage_common.c:193
 fsg_store_file+0x1a5/0x530 drivers/usb/gadget/function/storage_common.c:454
 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:2173 [inline]
 new_sync_write fs/read_write.c:507 [inline]
 vfs_write+0x748/0xd70 fs/read_write.c:594
 ksys_write+0x153/0x260 fs/read_write.c:647
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f0eb6f180d9
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:00007ffe12f2dac8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f0eb719ffa0 RCX: 00007f0eb6f180d9
RDX: 0000000000000005 RSI: 00002000000003c0 RDI: 0000000000000005
RBP: 00007f0eb6faf024 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f0eb719ffac R14: 00007f0eb719ffa0 R15: 00007f0eb719ffa0
 </TASK>
mass_storage.0/lun.0: file too small: file0

Crashes (17):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/08/22 04:56 linux-5.15.y 0eb903b5b519 1e72964b .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-linux-5-15-kasan possible deadlock in process_measurement
2026/08/11 05:49 linux-5.15.y aabd761612db 508909ea .config console log report syz / log [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in process_measurement
2026/09/24 03:16 linux-5.15.y 0248c33e835e 0281b448 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in process_measurement
2026/09/23 16:53 linux-5.15.y 0248c33e835e abce1216 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in process_measurement
2026/09/04 00:12 linux-5.15.y 0996e0926f6b 801f0966 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in process_measurement
2026/09/02 20:55 linux-5.15.y 0996e0926f6b 85995287 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in process_measurement
2026/08/25 17:06 linux-5.15.y 945fa863f02c a9a1fc32 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in process_measurement
2026/08/25 17:06 linux-5.15.y 945fa863f02c a9a1fc32 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in process_measurement
2026/08/25 17:03 linux-5.15.y 945fa863f02c a9a1fc32 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in process_measurement
2026/08/25 17:02 linux-5.15.y 945fa863f02c a9a1fc32 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in process_measurement
2026/08/25 17:02 linux-5.15.y 945fa863f02c a9a1fc32 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in process_measurement
2026/08/25 09:56 linux-5.15.y 945fa863f02c 614e416a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in process_measurement
2026/08/25 09:56 linux-5.15.y 945fa863f02c 614e416a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in process_measurement
2026/08/22 00:48 linux-5.15.y 0eb903b5b519 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in process_measurement
2026/08/10 21:45 linux-5.15.y aabd761612db 508909ea .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in process_measurement
2026/08/05 21:28 linux-5.15.y 6e2fd6534337 cd5b1963 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in process_measurement
2026/08/04 15:45 linux-5.15.y 6e2fd6534337 d4abbeac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in process_measurement
* Struck through repros no longer work on HEAD.