audit: type=1804 audit(1639817612.767:3): pid=9836 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.2" name="/root/syzkaller-testdir012440853/syzkaller.yAPpP9/16/file0/file0" dev="loop2" ino=3 res=1 ====================================================== WARNING: possible circular locking dependency detected 4.14.258-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.5/9846 is trying to acquire lock: (&table[i].mutex){+.+.}, at: [] nf_tables_netdev_event+0x10d/0x4d0 net/netfilter/nf_tables_netdev.c:122 but task is already holding lock: (rtnl_mutex){+.+.}, at: [] dev_ioctl+0x631/0xbe0 net/core/dev_ioctl.c:514 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (rtnl_mutex){+.+.}: __mutex_lock_common kernel/locking/mutex.c:756 [inline] __mutex_lock+0xc4/0x1310 kernel/locking/mutex.c:893 unregister_netdevice_notifier+0x5e/0x2b0 net/core/dev.c:1630 tee_tg_destroy+0x5c/0xb0 net/netfilter/xt_TEE.c:123 cleanup_entry+0x1fd/0x2d0 net/ipv4/netfilter/ip_tables.c:666 __do_replace+0x38d/0x570 net/ipv4/netfilter/ip_tables.c:1086 do_replace net/ipv4/netfilter/ip_tables.c:1142 [inline] do_ipt_set_ctl+0x256/0x3a0 net/ipv4/netfilter/ip_tables.c:1676 nf_sockopt net/netfilter/nf_sockopt.c:106 [inline] nf_setsockopt+0x5f/0xb0 net/netfilter/nf_sockopt.c:115 ip_setsockopt net/ipv4/ip_sockglue.c:1255 [inline] ip_setsockopt+0x94/0xb0 net/ipv4/ip_sockglue.c:1240 tcp_setsockopt+0x7b/0xc0 net/ipv4/tcp.c:2828 SYSC_setsockopt net/socket.c:1865 [inline] SyS_setsockopt+0x110/0x1e0 net/socket.c:1844 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x46/0xbb -> #1 (&xt[i].mutex){+.+.}: __mutex_lock_common kernel/locking/mutex.c:756 [inline] __mutex_lock+0xc4/0x1310 kernel/locking/mutex.c:893 target_revfn+0x43/0x210 net/netfilter/x_tables.c:354 xt_find_revision+0x15e/0x1d0 net/netfilter/x_tables.c:378 nfnl_compat_get+0x1f7/0x870 net/netfilter/nft_compat.c:678 nfnetlink_rcv_msg+0x9bb/0xc00 net/netfilter/nfnetlink.c:214 netlink_rcv_skb+0x125/0x390 net/netlink/af_netlink.c:2441 nfnetlink_rcv+0x1ab/0x1da0 net/netfilter/nfnetlink.c:515 netlink_unicast_kernel net/netlink/af_netlink.c:1294 [inline] netlink_unicast+0x437/0x610 net/netlink/af_netlink.c:1320 netlink_sendmsg+0x638/0xb90 net/netlink/af_netlink.c:1886 sock_sendmsg_nosec net/socket.c:646 [inline] sock_sendmsg+0xb5/0x100 net/socket.c:656 ___sys_sendmsg+0x6c8/0x800 net/socket.c:2062 __sys_sendmsg+0xa3/0x120 net/socket.c:2096 SYSC_sendmsg net/socket.c:2107 [inline] SyS_sendmsg+0x27/0x40 net/socket.c:2103 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x46/0xbb -> #0 (&table[i].mutex){+.+.}: lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998 __mutex_lock_common kernel/locking/mutex.c:756 [inline] __mutex_lock+0xc4/0x1310 kernel/locking/mutex.c:893 nf_tables_netdev_event+0x10d/0x4d0 net/netfilter/nf_tables_netdev.c:122 notifier_call_chain+0x108/0x1a0 kernel/notifier.c:93 call_netdevice_notifiers_info net/core/dev.c:1667 [inline] call_netdevice_notifiers net/core/dev.c:1683 [inline] dev_change_name+0x3ef/0x6a0 net/core/dev.c:1232 dev_ifsioc+0x2c2/0x7d0 net/core/dev_ioctl.c:323 dev_ioctl+0x63f/0xbe0 net/core/dev_ioctl.c:515 sock_do_ioctl net/socket.c:981 [inline] sock_ioctl+0x164/0x4c0 net/socket.c:1071 vfs_ioctl fs/ioctl.c:46 [inline] file_ioctl fs/ioctl.c:500 [inline] do_vfs_ioctl+0x75a/0xff0 fs/ioctl.c:684 SYSC_ioctl fs/ioctl.c:701 [inline] SyS_ioctl+0x7f/0xb0 fs/ioctl.c:692 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x46/0xbb other info that might help us debug this: Chain exists of: &table[i].mutex --> &xt[i].mutex --> rtnl_mutex Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(rtnl_mutex); lock(&xt[i].mutex); lock(rtnl_mutex); lock(&table[i].mutex); *** DEADLOCK *** 1 lock held by syz-executor.5/9846: #0: (rtnl_mutex){+.+.}, at: [] dev_ioctl+0x631/0xbe0 net/core/dev_ioctl.c:514 stack backtrace: CPU: 0 PID: 9846 Comm: syz-executor.5 Not tainted 4.14.258-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:17 [inline] dump_stack+0x1b2/0x281 lib/dump_stack.c:58 print_circular_bug.constprop.0.cold+0x2d7/0x41e kernel/locking/lockdep.c:1258 check_prev_add kernel/locking/lockdep.c:1905 [inline] check_prevs_add kernel/locking/lockdep.c:2022 [inline] validate_chain kernel/locking/lockdep.c:2464 [inline] __lock_acquire+0x2e0e/0x3f20 kernel/locking/lockdep.c:3491 lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998 __mutex_lock_common kernel/locking/mutex.c:756 [inline] __mutex_lock+0xc4/0x1310 kernel/locking/mutex.c:893 nf_tables_netdev_event+0x10d/0x4d0 net/netfilter/nf_tables_netdev.c:122 notifier_call_chain+0x108/0x1a0 kernel/notifier.c:93 call_netdevice_notifiers_info net/core/dev.c:1667 [inline] call_netdevice_notifiers net/core/dev.c:1683 [inline] dev_change_name+0x3ef/0x6a0 net/core/dev.c:1232 dev_ifsioc+0x2c2/0x7d0 net/core/dev_ioctl.c:323 dev_ioctl+0x63f/0xbe0 net/core/dev_ioctl.c:515 sock_do_ioctl net/socket.c:981 [inline] sock_ioctl+0x164/0x4c0 net/socket.c:1071 vfs_ioctl fs/ioctl.c:46 [inline] file_ioctl fs/ioctl.c:500 [inline] do_vfs_ioctl+0x75a/0xff0 fs/ioctl.c:684 SYSC_ioctl fs/ioctl.c:701 [inline] SyS_ioctl+0x7f/0xb0 fs/ioctl.c:692 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x46/0xbb RIP: 0033:0x7f043edaee99 RSP: 002b:00007f043d703168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f043eec2030 RCX: 00007f043edaee99 RDX: 0000000020000680 RSI: 0000000000008923 RDI: 0000000000000013 RBP: 00007f043ee08ff1 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffe6adb2bbf R14: 00007f043d703300 R15: 0000000000022000 ip_tables: iptables: counters copy to user failed while replacing table ip_tables: iptables: counters copy to user failed while replacing table syz-executor.0 (9863): drop_caches: 1 netlink: 660 bytes leftover after parsing attributes in process `syz-executor.1'. syz-executor.5 (9963): drop_caches: 2 syz-executor.0 (9951): drop_caches: 2 syz-executor.5 (9994): drop_caches: 2 syz-executor.0 (9993): drop_caches: 1 syz-executor.5 (10030): drop_caches: 2 syz-executor.0 (10032): drop_caches: 1 gfs2: not a GFS2 filesystem ptrace attach of "/root/syz-executor.3 exec"[8005] was attempted by "/root/syz-executor.3 exec"[10049] ptrace attach of "/root/syz-executor.3 exec"[8005] was attempted by "/root/syz-executor.3 exec"[10072] ptrace attach of "/root/syz-executor.3 exec"[8005] was attempted by "/root/syz-executor.3 exec"[10090] ptrace attach of "/root/syz-executor.3 exec"[8005] was attempted by "/root/syz-executor.3 exec"[10103] x_tables: ip6_tables: TCPOPTSTRIP target: only valid in mangle table, not raw L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details. x_tables: ip6_tables: TCPOPTSTRIP target: only valid in mangle table, not raw x_tables: ip6_tables: TCPOPTSTRIP target: only valid in mangle table, not raw x_tables: ip6_tables: TCPOPTSTRIP target: only valid in mangle table, not raw x_tables: ip6_tables: TCPOPTSTRIP target: only valid in mangle table, not raw netlink: 24 bytes leftover after parsing attributes in process `syz-executor.1'. x_tables: ip6_tables: TCPOPTSTRIP target: only valid in mangle table, not raw netlink: 4 bytes leftover after parsing attributes in process `syz-executor.0'. nft_compat: unsupported protocol 0 netlink: 3656 bytes leftover after parsing attributes in process `syz-executor.2'. x_tables: ip6_tables: TCPOPTSTRIP target: only valid in mangle table, not raw Unknown ioctl 1074013192 netlink: 660 bytes leftover after parsing attributes in process `syz-executor.0'. netlink: 828 bytes leftover after parsing attributes in process `syz-executor.2'. ptrace attach of "/root/syz-executor.0 exec"[8002] was attempted by "/root/syz-executor.0 exec"[10693] ptrace attach of "/root/syz-executor.0 exec"[8002] was attempted by "/root/syz-executor.0 exec"[10729] EXT4-fs (loop1): mounted filesystem without journal. Opts: ,errors=continue EXT4-fs (loop1): re-mounted. Opts: (null) ptrace attach of "/root/syz-executor.0 exec"[8002] was attempted by "/root/syz-executor.0 exec"[10748] EXT4-fs (loop4): mounted filesystem without journal. Opts: ,errors=continue EXT4-fs (loop1): mounted filesystem without journal. Opts: ,errors=continue EXT4-fs (loop1): re-mounted. Opts: (null) ptrace attach of "/root/syz-executor.0 exec"[8002] was attempted by "/root/syz-executor.0 exec"[10772]