- Vulnerability/
- CVE-2022-49205
CVE-2022-49205: bpf, sockmap: Fix double uncharge the mem of sk_msg
First published: Wed Feb 26 2025(Updated: )
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>
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/94c6ac22abcdede72bfaa0f4c22fb370891f4002
- https://git.kernel.org/stable/c/cd84ea3920aef936c559b63099ef0013ce6b2325
- https://git.kernel.org/stable/c/cb6f141ae705af0101e819065a79e6d029f6e393
- https://git.kernel.org/stable/c/223f3c51ab163852dd4819d357dcf33039929434
- https://git.kernel.org/stable/c/ac3ecb7760c750c8e4fc09c719241d8e6e88028c
- https://git.kernel.org/stable/c/2486ab434b2c2a14e9237296db00b1e1b7ae3273
Frequently Asked Questions
What is the severity of CVE-2022-49205?
CVE-2022-49205 is classified as a medium severity vulnerability in the Linux kernel.
How do I fix CVE-2022-49205?
To address CVE-2022-49205, users should update their Linux kernel to the latest stable version that has patched the vulnerability.
What are the potential impacts of CVE-2022-49205?
CVE-2022-49205 can lead to memory corruption issues if the affected functions are exploited during application tear down.
Which versions of the Linux Kernel are affected by CVE-2022-49205?
CVE-2022-49205 impacts various versions of the Linux kernel, specifically those prior to the patch release.
Is there a known exploit for CVE-2022-49205?
As of now, there are no publicly known exploits for CVE-2022-49205, but the vulnerability can still pose risks if unpatched.
- collector/mitre-cve
- source/MITRE
- collector/nvd-api
- source/NVD
- agent/first-publish-date
- agent/type
- agent/title
- agent/author
- agent/references
- agent/source
- agent/description
- agent/event
- agent/last-modified-date
- agent/softwarecombine
- agent/tags
- agent/guess-ai
- agent/software-canonical-lookup
- vendor/linux foundation
- canonical/linux kernel