{
  "cveId": "CVE-2022-50409",
  "url": "https://patchblox.com/security/cve/CVE-2022-50409",
  "summary": "CVE-2022-50409 is fixed in linux on 1 platform, first by DEBIAN-CVE-2022-50409, released September 18, 2025. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:  net: If sock is dead don\u0027t access sock\u0027s sk_wq i...",
  "description": "In the Linux kernel, the following vulnerability has been resolved:  net: If sock is dead don\u0027t access sock\u0027s sk_wq in sk_stream_wait_memory  Fixes the below NULL pointer dereference:    [...]   [   14.471200] Call Trace:   [   14.471562]  \u003CTASK\u003E   [   14.471882]  lock_acquire\u002B0x245/0x2e0   [   14.472416]  ? remove_wait_queue\u002B0x12/0x50   [   14.473014]  ? _raw_spin_lock_irqsave\u002B0x17/0x50   [   14.473681]  _raw_spin_lock_irqsave\u002B0x3d/0x50   [   14.474318]  ? remove_wait_queue\u002B0x12/0x50   [   14.474907]  remove_wait_queue\u002B0x12/0x50   [   14.475480]  sk_stream_wait_memory\u002B0x20d/0x340   [   14.476127]  ? do_wait_intr_irq\u002B0x80/0x80   [   14.476704]  do_tcp_sendpages\u002B0x287/0x600   [   14.477283]  tcp_bpf_push\u002B0xab/0x260   [   14.477817]  tcp_bpf_sendmsg_redir\u002B0x297/0x500   [   14.478461]  ? __local_bh_enable_ip\u002B0x77/0xe0   [   14.479096]  tcp_bpf_send_verdict\u002B0x105/0x470   [   14.479729]  tcp_bpf_sendmsg\u002B0x318/0x4f0   [   14.480311]  sock_sendmsg\u002B0x2d/0x40   [   14.480822]  ____sys_sendmsg\u002B0x1b4/0x1c0   [   14.481390]  ? copy_msghdr_from_user\u002B0x62/0x80   [   14.482048]  ___sys_sendmsg\u002B0x78/0xb0   [   14.482580]  ? vmf_insert_pfn_prot\u002B0x91/0x150   [   14.483215]  ? __do_fault\u002B0x2a/0x1a0   [   14.483738]  ? do_fault\u002B0x15e/0x5d0   [   14.484246]  ? __handle_mm_fault\u002B0x56b/0x1040   [   14.484874]  ? lock_is_held_type\u002B0xdf/0x130   [   14.485474]  ? find_held_lock\u002B0x2d/0x90   [   14.486046]  ? __sys_sendmsg\u002B0x41/0x70   [   14.486587]  __sys_sendmsg\u002B0x41/0x70   [   14.487105]  ? intel_pmu_drain_pebs_core\u002B0x350/0x350   [   14.487822]  do_syscall_64\u002B0x34/0x80   [   14.488345]  entry_SYSCALL_64_after_hwframe\u002B0x63/0xcd   [...]  The test scenario has the following flow:  thread1                               thread2 -----------                           ---------------  tcp_bpf_sendmsg   tcp_bpf_send_verdict    tcp_bpf_sendmsg_redir              sock_close     tcp_bpf_push_locked                 __sock_release      tcp_bpf_push                         //inet_release       do_tcp_sendpages                    sock-\u003Eops-\u003Erelease        sk_stream_wait_memory          \t   // tcp_close           sk_wait_event                      sk-\u003Esk_prot-\u003Eclose            release_sock(__sk);             ***                                                 lock_sock(sk);                                                   __tcp_close                                                     sock_orphan(sk)                                                       sk-\u003Esk_wq  = NULL                                                 release_sock             ****            lock_sock(__sk);           remove_wait_queue(sk_sleep(sk), \u0026wait);              sk_sleep(sk)              //NULL pointer dereference              \u0026rcu_dereference_raw(sk-\u003Esk_wq)-\u003Ewait  While waiting for memory in thread1, the socket is released with its wait queue because thread2 has closed it. This caused by tcp_bpf_send_verdict didn\u0027t increase the f_count of psock-\u003Esk_redir-\u003Esk_socket-\u003Efile in thread1.  We should check if SOCK_DEAD flag is set on wakeup in sk_stream_wait_memory before accessing the wait queue.",
  "published": "2025-09-18T16:15:44Z",
  "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.0016,
  "epssPercentile": 0.05153,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 12.15 (bookworm)",
      "fixedVersion": "6.0.3-1",
      "fix": "DEBIAN-CVE-2022-50409",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-50409",
      "released": "2025-09-18T16:15:44Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "6.0.3-1",
      "fix": "DEBIAN-CVE-2022-50409",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-50409",
      "released": "2025-09-18T16:15:44Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "6.0.3-1",
      "fix": "DEBIAN-CVE-2022-50409",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-50409",
      "released": "2025-09-18T16:15:44Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-08T00:53:09Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}