{
  "cveId": "CVE-2022-49209",
  "url": "https://patchblox.com/security/cve/CVE-2022-49209",
  "summary": "CVE-2022-49209 is fixed in linux on 1 platform, first by DEBIAN-CVE-2022-49209, released February 26, 2025. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:  bpf, sockmap: Fix memleak in tcp_bpf_sendmsg whi...",
  "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-\u003Esg.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\u002B0xd4/0x1a0 Call Trace:  \u003CTASK\u003E  inet_csk_destroy_sock\u002B0x55/0x110  __tcp_close\u002B0x279/0x470  tcp_close\u002B0x1f/0x60  inet_release\u002B0x3f/0x80  __sock_release\u002B0x3d/0xb0  sock_close\u002B0x11/0x20  __fput\u002B0x92/0x250  task_work_run\u002B0x6a/0xa0  do_exit\u002B0x33b/0xb60  do_group_exit\u002B0x2f/0xa0  get_signal\u002B0xb6/0x950  arch_do_signal_or_restart\u002B0xac/0x2a0  exit_to_user_mode_prepare\u002B0xa9/0x200  syscall_exit_to_user_mode\u002B0x12/0x30  do_syscall_64\u002B0x46/0x80  entry_SYSCALL_64_after_hwframe\u002B0x44/0xae  \u003C/TASK\u003E  WARNING: CPU: 3 PID: 2094 at net/ipv4/af_inet.c:155 inet_sock_destruct\u002B0x13c/0x260 Call Trace:  \u003CTASK\u003E  __sk_destruct\u002B0x24/0x1f0  sk_psock_destroy\u002B0x19b/0x1c0  process_one_work\u002B0x1b3/0x3c0  kthread\u002B0xe6/0x110  ret_from_fork\u002B0x22/0x30  \u003C/TASK\u003E",
  "published": "2025-02-26T07:00:58Z",
  "severity": "medium",
  "cvss": 5.5,
  "cvssVector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
  "epss": 0.00269,
  "epssPercentile": 0.19228,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 12.15 (bookworm)",
      "fixedVersion": "5.17.3-1",
      "fix": "DEBIAN-CVE-2022-49209",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-49209",
      "released": "2025-02-26T07:00:58Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "5.17.3-1",
      "fix": "DEBIAN-CVE-2022-49209",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-49209",
      "released": "2025-02-26T07:00:58Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "5.17.3-1",
      "fix": "DEBIAN-CVE-2022-49209",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-49209",
      "released": "2025-02-26T07:00:58Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-08T06:59:42Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}