bpf, sockmap: Fix memleak in tcp_bpf_sendmsg while sk msg is full

Description

In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Fix memleak in tcp_bpf_sendmsg while sk msg is full If tcp_bpf_sendmsg() is running while sk msg is full. When sk_msg_alloc() returns -ENOMEM error, tcp_bpf_sendmsg() goes to wait_for_memory. If partial memory has been alloced by sk_msg_alloc(), that is, msg_tx->sg.size is greater than osize after sk_msg_alloc(), memleak occurs. To fix we use sk_msg_trim() to release the allocated memory, then goto wait for memory. Other call paths of sk_msg_alloc() have the similar issue, such as tls_sw_sendmsg(), so handle sk_msg_trim logic inside sk_msg_alloc(), as Cong Wang suggested. This issue can cause the following info: WARNING: CPU: 3 PID: 7950 at net/core/stream.c:208 sk_stream_kill_queues+0xd4/0x1a0 Call Trace: <TASK> inet_csk_destroy_sock+0x55/0x110 __tcp_close+0x279/0x470 tcp_close+0x1f/0x60 inet_release+0x3f/0x80 __sock_release+0x3d/0xb0 sock_close+0x11/0x20 __fput+0x92/0x250 task_work_run+0x6a/0xa0 do_exit+0x33b/0xb60 do_group_exit+0x2f/0xa0 get_signal+0xb6/0x950 arch_do_signal_or_restart+0xac/0x2a0 exit_to_user_mode_prepare+0xa9/0x200 syscall_exit_to_user_mode+0x12/0x30 do_syscall_64+0x46/0x80 entry_SYSCALL_64_after_hwframe+0x44/0xae </TASK> WARNING: CPU: 3 PID: 2094 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 kthread+0xe6/0x110 ret_from_fork+0x22/0x30 </TASK>

Timeline

Scores

EPSS (exploitation in 30 days)

0.27% · top 81% of all CVEs (7 Nov 2026)

CISA SSVC

Exploitation: none · Automatable: no · Technical impact: partial

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Weakness

• CWE-401 Missing Release of Memory after Effective Lifetime (opens in a new tab)All about CWE-401 and its CVEs

Affected products

• Linux · Linux

  • affected 604326b41a6fb9b4a78b6179335decee0365cd8c – < 6d03722c34d9603df325f67c6d30dc1b7b3c6067
  • affected 604326b41a6fb9b4a78b6179335decee0365cd8c – < bec34a91eba3483e1830c02bdd36f8f968642047
  • affected 604326b41a6fb9b4a78b6179335decee0365cd8c – < de3a8d8fab0710186f7864ec812836d8d70da3c9
  • affected 604326b41a6fb9b4a78b6179335decee0365cd8c – < f677328f05f52d535cbdc15cb04476db49477eb4
  • affected 604326b41a6fb9b4a78b6179335decee0365cd8c – < d0b85dfc6f01d26808e2576c6537c131b590e270
  • affected 604326b41a6fb9b4a78b6179335decee0365cd8c – < 9c34e38c4a870eb30b13f42f5b44f42e9d19ccb8

• Linux · Linux

  • affected 4.20
  • unaffected < 4.20
  • unaffected 5.4.189 – ≤ 5.4.*
  • unaffected 5.10.110 – ≤ 5.10.*
  • unaffected 5.15.33 – ≤ 5.15.*
  • unaffected 5.16.19 – ≤ 5.16.*
  • unaffected 5.17.2 – ≤ 5.17.*
  • unaffected 5.18 – ≤ *

References (6)

• https://git.kernel.org/stable/c/6d03722c34d9603df325f67c6d30dc1b7b3c6067 (opens in a new tab)
• https://git.kernel.org/stable/c/bec34a91eba3483e1830c02bdd36f8f968642047 (opens in a new tab)
• https://git.kernel.org/stable/c/de3a8d8fab0710186f7864ec812836d8d70da3c9 (opens in a new tab)
• https://git.kernel.org/stable/c/f677328f05f52d535cbdc15cb04476db49477eb4 (opens in a new tab)
• https://git.kernel.org/stable/c/d0b85dfc6f01d26808e2576c6537c131b590e270 (opens in a new tab)
• https://git.kernel.org/stable/c/9c34e38c4a870eb30b13f42f5b44f42e9d19ccb8 (opens in a new tab)

Sources

The same CVE in the primary databases and aggregators, to check against.

• CVE.org record (opens in a new tab)
• CVE List JSON (GitHub) (opens in a new tab)
• NVD (opens in a new tab)
• FIRST EPSS (opens in a new tab)
• OSV.dev (opens in a new tab)
• GitHub Advisories (opens in a new tab)
• CIRCL Vulnerability-Lookup (opens in a new tab)

Badge for a README or a ticket

[![CVE-2022-49209](https://trackcve.app/badge/CVE-2022-49209.svg)](https://trackcve.app/cve/CVE-2022-49209)

Record last updated 11 May 2026, 18:55 UTC.