CVE-2022-49204

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> bpf, sockmap: Fix more uncharged while msg has more_data<br /> <br /> In tcp_bpf_send_verdict(), if msg has more data after<br /> tcp_bpf_sendmsg_redir():<br /> <br /> tcp_bpf_send_verdict()<br /> tosend = msg-&gt;sg.size //msg-&gt;sg.size = 22220<br /> case __SK_REDIRECT:<br /> sk_msg_return() //uncharged msg-&gt;sg.size(22220) sk-&gt;sk_forward_alloc<br /> tcp_bpf_sendmsg_redir() //after tcp_bpf_sendmsg_redir, msg-&gt;sg.size=11000<br /> goto more_data;<br /> tosend = msg-&gt;sg.size //msg-&gt;sg.size = 11000<br /> case __SK_REDIRECT:<br /> sk_msg_return() //uncharged msg-&gt;sg.size(11000) to sk-&gt;sk_forward_alloc<br /> <br /> The msg-&gt;sg.size(11000) has been uncharged twice, to fix we can charge the<br /> remaining msg-&gt;sg.size before goto more data.<br /> <br /> This issue can cause the following info:<br /> WARNING: CPU: 0 PID: 9860 at net/core/stream.c:208 sk_stream_kill_queues+0xd4/0x1a0<br /> Call Trace:<br /> <br /> inet_csk_destroy_sock+0x55/0x110<br /> __tcp_close+0x279/0x470<br /> tcp_close+0x1f/0x60<br /> inet_release+0x3f/0x80<br /> __sock_release+0x3d/0xb0<br /> sock_close+0x11/0x20<br /> __fput+0x92/0x250<br /> task_work_run+0x6a/0xa0<br /> do_exit+0x33b/0xb60<br /> do_group_exit+0x2f/0xa0<br /> get_signal+0xb6/0x950<br /> arch_do_signal_or_restart+0xac/0x2a0<br /> ? vfs_write+0x237/0x290<br /> exit_to_user_mode_prepare+0xa9/0x200<br /> syscall_exit_to_user_mode+0x12/0x30<br /> do_syscall_64+0x46/0x80<br /> entry_SYSCALL_64_after_hwframe+0x44/0xae<br /> <br /> <br /> WARNING: CPU: 0 PID: 2136 at net/ipv4/af_inet.c:155 inet_sock_destruct+0x13c/0x260<br /> Call Trace:<br /> <br /> __sk_destruct+0x24/0x1f0<br /> sk_psock_destroy+0x19b/0x1c0<br /> process_one_work+0x1b3/0x3c0<br /> worker_thread+0x30/0x350<br /> ? process_one_work+0x3c0/0x3c0<br /> kthread+0xe6/0x110<br /> ? kthread_complete_and_exit+0x20/0x20<br /> ret_from_fork+0x22/0x30<br />