CVE-2022-49205 Details
Description
In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Fix double uncharge the mem of sk_msg If tcp_bpf_sendmsg is running during a tear down operation, psock may be freed. tcp_bpf_sendmsg() tcp_bpf_send_verdict() sk_msg_return() tcp_bpf_sendmsg_redir() unlikely(!psock)) sk_msg_free() The mem of msg has been uncharged in tcp_bpf_send_verdict() by sk_msg_return(), and would be uncharged by sk_msg_free() again. When psock is null, we can simply returning an error code, this would then trigger the sk_msg_free_nocharge in the error path of __SK_REDIRECT and would have the side effect of throwing an error up to user space. This would be a slight change in behavior from user side but would look the same as an error if the redirect on the socket threw an error. This issue can cause the following info: WARNING: CPU: 0 PID: 2136 at net/ipv4/af_inet.c:155 inet_sock_destruct+0x13c/0x260 Call Trace: <TASK> __sk_destruct+0x24/0x1f0 sk_psock_destroy+0x19b/0x1c0 process_one_work+0x1b3/0x3c0 worker_thread+0x30/0x350 ? process_one_work+0x3c0/0x3c0 kthread+0xe6/0x110 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x22/0x30 </TASK>
A vulnerability in the Linux kernel's BPF sockmap implementation can lead to improper memory management. During the teardown of a socket, the memory associated with sk_msg can be double uncharged, potentially allowing for use-after-free conditions. This issue arises when tcp_bpf_sendmsg is called while a socket is being torn down, leading to sk_msg_return uncharging the message memory, followed by sk_msg_free, creating a risk of freeing memory that is still in use.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/223f3c51ab163852dd4819d357dcf33039929434 | kernel.org | Patch |
| https://git.kernel.org/stable/c/2486ab434b2c2a14e9237296db00b1e1b7ae3273 | kernel.org | Patch |
| https://git.kernel.org/stable/c/94c6ac22abcdede72bfaa0f4c22fb370891f4002 | kernel.org | Patch |
| https://git.kernel.org/stable/c/ac3ecb7760c750c8e4fc09c719241d8e6e88028c | kernel.org | Patch |
| https://git.kernel.org/stable/c/cb6f141ae705af0101e819065a79e6d029f6e393 | kernel.org | Patch |
| https://git.kernel.org/stable/c/cd84ea3920aef936c559b63099ef0013ce6b2325 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-415 | Double Free | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 4.20, < 5.4.189 >= 5.5, < 5.10.110 >= 5.11, < 5.15.33 >= 5.16, < 5.16.19 >= 5.17, < 5.17.2 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Sep 22, 2025 | Initial Analysis | [email protected] |
| Feb 26, 2025 | New CVE Received | kernel.org |