In the Linux kernel, the following vulnerability has been resolved:<\/p>\n
tipc: restrict socket queue dumps in enqueue tracepoints<\/p>\n
tipc_sk_enqueue() runs with sk->sk_lock.slock held while the socket is
\nowned by user context. The spinlock protects the backlog queue in this
\npath, but it does not serialize against the socket owner consuming or
\npurging sk_receive_queue.<\/p>\n
KASAN reported:<\/p>\n
CPU: 14 UID: 0 PID: 1050 Comm: tipc3 Not tainted 7.1.0-rc6+ #126 PREEMPT(lazy)
\n Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04\/01\/2014
\n Call Trace:<\/p>\n
dump_stack_lvl+0x76\/0xa0 lib\/dump_stack.c:123
\n print_report+0xce\/0x5b0 mm\/kasan\/report.c:482
\n kasan_report+0xc6\/0x100 mm\/kasan\/report.c:597
\n __asan_report_load4_noabort+0x14\/0x30 mm\/kasan\/report_generic.c:380
\n tipc_skb_dump+0x1327\/0x16f0 net\/tipc\/trace.c:73
\n tipc_list_dump+0x208\/0x2e0 net\/tipc\/trace.c:187
\n tipc_sk_dump+0xaf6\/0xd60 net\/tipc\/socket.c:3996
\n trace_event_raw_event_tipc_sk_class+0x312\/0x5a0 net\/tipc\/trace.h:188
\n tipc_sk_rcv+0xb1d\/0x1d50 net\/tipc\/socket.c:2497
\n tipc_node_xmit+0x1c3\/0x1440 net\/tipc\/node.c:1689
\n __tipc_sendmsg+0x97a\/0x1440 net\/tipc\/socket.c:1512
\n tipc_sendmsg+0x52\/0x80 net\/tipc\/socket.c:1400
\n sock_sendmsg+0x2f6\/0x3e0 net\/socket.c:825
\n splice_to_socket+0x7f9\/0x1010 fs\/splice.c:884
\n do_splice+0xe21\/0x2330 fs\/splice.c:936
\n __do_splice+0x153\/0x260 fs\/splice.c:1431
\n __x64_sys_splice+0x150\/0x230 fs\/splice.c:1616
\n x64_sys_call+0xeb5\/0x2790 arch\/x86\/entry\/syscall_64.c:41
\n do_syscall_64+0xf3\/0x620 arch\/x86\/entry\/syscall_64.c:63
\n entry_SYSCALL_64_after_hwframe+0x76\/0x7e arch\/x86\/entry\/entry_64.S:130
\n RIP: 0033:0x71624e8aafe2
\n Code: 08 0f 85 71 3a ff ff 49 89 fb 48 89 f0 48 89 d7 48 89 ce 4c 89 c2 4d 89 ca 4c 8b 44 24 08 4c 8b 4c 24 10 4c 89 5c 24 08 0f 05 66 2e 0f 1f 84 00 00 00 00 00 66 2e 0f 1f 84 00 00 00 00 00 66
\n RSP: 002b:0000716157ffed68 EFLAGS: 00000246 ORIG_RAX: 0000000000000113
\n RAX: ffffffffffffffda RBX: 0000716157fff6c0 RCX: 000071624e8aafe2
\n RDX: 000000000000005f RSI: 0000000000000000 RDI: 0000000000000066
\n RBP: 0000716157ffed90 R08: 0000000000008000 R09: 0000000000000001
\n R10: 0000000000000000 R11: 0000000000000246 R12: ffffffffffffff00
\n R13: 0000000000000021 R14: 0000000000000000 R15: 00007fff89799c40<\/p>\n
The TIPC_DUMP_ALL tracepoints in tipc_sk_enqueue() also dump
\nsk_receive_queue and can therefore dereference skbs that the socket
\nowner has already dequeued or freed. Restrict these dumps to
\nTIPC_DUMP_SK_BKLGQ, which matches the queue protected by the held
\nspinlock.<\/p>\n
Keep the change limited to the enqueue path, where the unsafe queue dump
\nis reachable while the socket is owned by user context.<\/p>\n","protected":false},"excerpt":{"rendered":"
In the Linux kernel, the following vulnerability has been resolved:<\/p>\n
tipc: restrict socket queue dumps in enqueue tracepoints<\/p>\n
tipc_sk_enqueue() runs with sk->sk_lock.slock held while the socket is
\now<\/p>\n","protected":false},"template":"","meta":[],"categories":[],"tags":[],"class_list":["post-6923","vuln","type-vuln","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln\/6923","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln"}],"about":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/types\/vuln"}],"wp:attachment":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=6923"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=6923"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=6923"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}