======================================================
WARNING: possible circular locking dependency detected
4.14.259-syzkaller #0 Not tainted
------------------------------------------------------
syz-executor.4/10429 is trying to acquire lock:
(&table[i].mutex){+.+.}, at: [<ffffffff85f024cd>] nf_tables_netdev_event+0x10d/0x4d0 net/netfilter/nf_tables_netdev.c:122
but task is already holding lock:
(rtnl_mutex){+.+.}, at: [<ffffffff83d53bd4>] tun_detach drivers/net/tun.c:593 [inline]
(rtnl_mutex){+.+.}, at: [<ffffffff83d53bd4>] tun_chr_close+0x34/0x60 drivers/net/tun.c:2732
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+0x232/0x310 net/ipv6/netfilter/ip6_tables.c:685
__do_replace+0x38d/0x580 net/ipv6/netfilter/ip6_tables.c:1106
do_replace net/ipv6/netfilter/ip6_tables.c:1162 [inline]
do_ip6t_set_ctl+0x256/0x3b0 net/ipv6/netfilter/ip6_tables.c:1688
nf_sockopt net/netfilter/nf_sockopt.c:106 [inline]
nf_setsockopt+0x5f/0xb0 net/netfilter/nf_sockopt.c:115
ipv6_setsockopt+0xc0/0x120 net/ipv6/ipv6_sockglue.c:937
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
match_revfn+0x43/0x210 net/netfilter/x_tables.c:332
xt_find_revision+0x8d/0x1d0 net/netfilter/x_tables.c:380
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:2446
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+0x648/0xbc0 net/netlink/af_netlink.c:1891
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]
rollback_registered_many+0x765/0xba0 net/core/dev.c:7211
rollback_registered+0xca/0x170 net/core/dev.c:7253
unregister_netdevice_queue+0x1b4/0x360 net/core/dev.c:8274
unregister_netdevice include/linux/netdevice.h:2443 [inline]
__tun_detach+0xca2/0xf60 drivers/net/tun.c:584
tun_detach drivers/net/tun.c:594 [inline]
tun_chr_close+0x41/0x60 drivers/net/tun.c:2732
__fput+0x25f/0x7a0 fs/file_table.c:210
task_work_run+0x11f/0x190 kernel/task_work.c:113
tracehook_notify_resume include/linux/tracehook.h:191 [inline]
exit_to_usermode_loop+0x1ad/0x200 arch/x86/entry/common.c:164
prepare_exit_to_usermode arch/x86/entry/common.c:199 [inline]
syscall_return_slowpath arch/x86/entry/common.c:270 [inline]
do_syscall_64+0x4a3/0x640 arch/x86/entry/common.c:297
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.4/10429:
#0: (rtnl_mutex){+.+.}, at: [<ffffffff83d53bd4>] tun_detach drivers/net/tun.c:593 [inline]
#0: (rtnl_mutex){+.+.}, at: [<ffffffff83d53bd4>] tun_chr_close+0x34/0x60 drivers/net/tun.c:2732
stack backtrace:
CPU: 0 PID: 10429 Comm: syz-executor.4 Not tainted 4.14.259-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]
rollback_registered_many+0x765/0xba0 net/core/dev.c:7211
rollback_registered+0xca/0x170 net/core/dev.c:7253
unregister_netdevice_queue+0x1b4/0x360 net/core/dev.c:8274
unregister_netdevice include/linux/netdevice.h:2443 [inline]
__tun_detach+0xca2/0xf60 drivers/net/tun.c:584
tun_detach drivers/net/tun.c:594 [inline]
tun_chr_close+0x41/0x60 drivers/net/tun.c:2732
__fput+0x25f/0x7a0 fs/file_table.c:210
task_work_run+0x11f/0x190 kernel/task_work.c:113
tracehook_notify_resume include/linux/tracehook.h:191 [inline]
exit_to_usermode_loop+0x1ad/0x200 arch/x86/entry/common.c:164
prepare_exit_to_usermode arch/x86/entry/common.c:199 [inline]
syscall_return_slowpath arch/x86/entry/common.c:270 [inline]
do_syscall_64+0x4a3/0x640 arch/x86/entry/common.c:297
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x7f4f74846adb
RSP: 002b:00007ffdbd307000 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000004 RCX: 00007f4f74846adb
RDX: 00007f4f749ab420 RSI: ffffffffffffffff RDI: 0000000000000003
RBP: 00007f4f749a8960 R08: 0000000000000000 R09: 00007f4f749ab428
R10: 00007ffdbd307100 R11: 0000000000000293 R12: 0000000000030080
R13: 00007ffdbd307100 R14: 00007f4f749a6f60 R15: 0000000000000032
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.
kauditd_printk_skb: 5873 callbacks suppressed
audit: type=1800 audit(1640515229.773:25140): pid=10466 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed" comm="syz-executor.1" name="SYSV00000000" dev="hugetlbfs" ino=0 res=0
audit: type=1800 audit(1640515229.953:25141): pid=10491 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed" comm="syz-executor.1" name="SYSV00000000" dev="hugetlbfs" ino=32769 res=0
audit: type=1800 audit(1640515229.983:25142): pid=10505 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed" comm="syz-executor.3" name="SYSV00000000" dev="hugetlbfs" ino=0 res=0
audit: type=1800 audit(1640515230.003:25143): pid=10499 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed" comm="syz-executor.5" name="SYSV00000000" dev="hugetlbfs" ino=0 res=0
audit: type=1800 audit(1640515230.033:25144): pid=10509 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed" comm="syz-executor.2" name="SYSV00000000" dev="hugetlbfs" ino=0 res=0
audit: type=1800 audit(1640515230.123:25145): pid=10523 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed" comm="syz-executor.3" name="SYSV00000000" dev="hugetlbfs" ino=32769 res=0
audit: type=1800 audit(1640515230.173:25146): pid=10539 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed" comm="syz-executor.5" name="SYSV00000000" dev="hugetlbfs" ino=32769 res=0
audit: type=1800 audit(1640515230.173:25147): pid=10543 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed" comm="syz-executor.2" name="SYSV00000000" dev="hugetlbfs" ino=32769 res=0
audit: type=1800 audit(1640515230.173:25148): pid=10527 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed" comm="syz-executor.1" name="SYSV00000000" dev="hugetlbfs" ino=65538 res=0
audit: type=1800 audit(1640515230.293:25149): pid=10573 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed" comm="syz-executor.2" name="SYSV00000000" dev="hugetlbfs" ino=65538 res=0
======================================================
WARNING: the mand mount option is being deprecated and
will be removed in v5.15!
======================================================
vxfs: unable to read disk superblock at 1
vxfs: unable to read disk superblock at 8
EXT4-fs (loop2): Unsupported blocksize for fs encryption
vxfs: can't find superblock.
vxfs: unable to read disk superblock at 1
vxfs: unable to read disk superblock at 8
vxfs: can't find superblock.
EXT4-fs (loop2): Unsupported blocksize for fs encryption
EXT4-fs (loop2): Unsupported blocksize for fs encryption
vxfs: unable to read disk superblock at 1
vxfs: unable to read disk superblock at 8
vxfs: can't find superblock.
EXT4-fs (loop2): Unsupported blocksize for fs encryption
print_req_error: I/O error, dev loop2, sector 0
Buffer I/O error on dev loop2, logical block 0, async page read
print_req_error: I/O error, dev loop2, sector 6
Buffer I/O error on dev loop2, logical block 3, async page read
vxfs: unable to read disk superblock at 1
vxfs: unable to read disk superblock at 8
vxfs: can't find superblock.
EXT4-fs (loop0): Test dummy encryption mount option ignored
EXT4-fs (loop0): mounted filesystem without journal. Opts: test_dummy_encryption,,errors=continue
EXT4-fs (loop5): Test dummy encryption mount option ignored
EXT4-fs (loop0): Test dummy encryption mount option ignored
EXT4-fs (loop0): mounted filesystem without journal. Opts: test_dummy_encryption,,errors=continue
EXT4-fs (loop5): mounted filesystem without journal. Opts: test_dummy_encryption,,errors=continue
EXT4-fs (loop1): Test dummy encryption mount option ignored
EXT4-fs (loop1): mounted filesystem without journal. Opts: test_dummy_encryption,,errors=continue
EXT4-fs (loop5): Test dummy encryption mount option ignored
EXT4-fs (loop0): Test dummy encryption mount option ignored
EXT4-fs (loop5): mounted filesystem without journal. Opts: test_dummy_encryption,,errors=continue
EXT4-fs (loop0): mounted filesystem without journal. Opts: test_dummy_encryption,,errors=continue
EXT4-fs (loop1): Test dummy encryption mount option ignored
EXT4-fs (loop1): mounted filesystem without journal. Opts: test_dummy_encryption,,errors=continue
EXT4-fs (loop0): Test dummy encryption mount option ignored
EXT4-fs (loop1): Test dummy encryption mount option ignored
EXT4-fs (loop5): Test dummy encryption mount option ignored
EXT4-fs (loop1): mounted filesystem without journal. Opts: test_dummy_encryption,,errors=continue
EXT4-fs (loop0): mounted filesystem without journal. Opts: test_dummy_encryption,,errors=continue
EXT4-fs (loop5): mounted filesystem without journal. Opts: test_dummy_encryption,,errors=continue
UDF-fs: error (device loop4): udf_process_sequence: Block 99 of volume descriptor sequence is corrupted or we could not read it
UDF-fs: error (device loop4): udf_process_sequence: Block 1984 of volume descriptor sequence is corrupted or we could not read it
UDF-fs: Scanning with blocksize 512 failed
UDF-fs: warning (device loop4): udf_load_vrs: No anchor found
UDF-fs: Scanning with blocksize 1024 failed
UDF-fs: warning (device loop4): udf_load_vrs: No anchor found
UDF-fs: Scanning with blocksize 2048 failed
UDF-fs: warning (device loop4): udf_load_vrs: No VRS found
UDF-fs: Scanning with blocksize 4096 failed
UDF-fs: error (device loop4): udf_process_sequence: Block 99 of volume descriptor sequence is corrupted or we could not read it
UDF-fs: error (device loop4): udf_process_sequence: Block 1984 of volume descriptor sequence is corrupted or we could not read it
UDF-fs: Scanning with blocksize 512 failed
UDF-fs: warning (device loop4): udf_load_vrs: No anchor found
UDF-fs: Scanning with blocksize 1024 failed
UDF-fs: warning (device loop4): udf_load_vrs: No anchor found
UDF-fs: Scanning with blocksize 2048 failed
UDF-fs: warning (device loop4): udf_load_vrs: No VRS found
UDF-fs: Scanning with blocksize 4096 failed
UDF-fs: error (device loop4): udf_process_sequence: Block 99 of volume descriptor sequence is corrupted or we could not read it
UDF-fs: error (device loop4): udf_process_sequence: Block 1984 of volume descriptor sequence is corrupted or we could not read it
UDF-fs: Scanning with blocksize 512 failed
UDF-fs: warning (device loop4): udf_load_vrs: No anchor found
UDF-fs: Scanning with blocksize 1024 failed
UDF-fs: warning (device loop4): udf_load_vrs: No anchor found
UDF-fs: Scanning with blocksize 2048 failed
UDF-fs: warning (device loop4): udf_load_vrs: No VRS found
UDF-fs: Scanning with blocksize 4096 failed
UDF-fs: error (device loop4): udf_process_sequence: Block 99 of volume descriptor sequence is corrupted or we could not read it
UDF-fs: error (device loop4): udf_process_sequence: Block 1984 of volume descriptor sequence is corrupted or we could not read it
UDF-fs: Scanning with blocksize 512 failed
UDF-fs: warning (device loop4): udf_load_vrs: No anchor found
UDF-fs: Scanning with blocksize 1024 failed
UDF-fs: warning (device loop4): udf_load_vrs: No anchor found
UDF-fs: Scanning with blocksize 2048 failed
UDF-fs: warning (device loop4): udf_load_vrs: No VRS found
UDF-fs: Scanning with blocksize 4096 failed