{"id":"CVE-2022-50459","summary":"scsi: iscsi: iscsi_tcp: Fix null-ptr-deref while calling getpeername()","details":"In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: iscsi: iscsi_tcp: Fix null-ptr-deref while calling getpeername()\n\nFix a NULL pointer crash that occurs when we are freeing the socket at the\nsame time we access it via sysfs.\n\nThe problem is that:\n\n 1. iscsi_sw_tcp_conn_get_param() and iscsi_sw_tcp_host_get_param() take\n    the frwd_lock and do sock_hold() then drop the frwd_lock. sock_hold()\n    does a get on the \"struct sock\".\n\n 2. iscsi_sw_tcp_release_conn() does sockfd_put() which does the last put\n    on the \"struct socket\" and that does __sock_release() which sets the\n    sock-\u003eops to NULL.\n\n 3. iscsi_sw_tcp_conn_get_param() and iscsi_sw_tcp_host_get_param() then\n    call kernel_getpeername() which accesses the NULL sock-\u003eops.\n\nAbove we do a get on the \"struct sock\", but we needed a get on the \"struct\nsocket\". Originally, we just held the frwd_lock the entire time but in\ncommit bcf3a2953d36 (\"scsi: iscsi: iscsi_tcp: Avoid holding spinlock while\ncalling getpeername()\") we switched to refcount based because the network\nlayer changed and started taking a mutex in that path, so we could no\nlonger hold the frwd_lock.\n\nInstead of trying to maintain multiple refcounts, this just has us use a\nmutex for accessing the socket in the interface code paths.","modified":"2026-03-20T11:47:28.541758Z","published":"2025-10-01T11:45:31.740Z","related":["SUSE-SU-2025:03613-1","SUSE-SU-2025:03615-1","SUSE-SU-2025:03626-1","SUSE-SU-2025:03628-1","SUSE-SU-2025:3716-1","SUSE-SU-2025:3761-1","SUSE-SU-2025:4189-1"],"database_specific":{"osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/50xxx/CVE-2022-50459.json","cna_assigner":"Linux"},"references":[{"type":"WEB","url":"https://git.kernel.org/stable/c/0a0b861fce2657ba08ec356a74346b37ca4b2008"},{"type":"WEB","url":"https://git.kernel.org/stable/c/57569c37f0add1b6489e1a1563c71519daf732cf"},{"type":"WEB","url":"https://git.kernel.org/stable/c/884a788f065578bb640382279a83d1df433b13e6"},{"type":"WEB","url":"https://git.kernel.org/stable/c/897dbbc57d71e8a34ec1af8e573a142de457da38"},{"type":"WEB","url":"https://git.kernel.org/stable/c/a26b0658751bb0a3b28386fca715333b104d32a2"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/50xxx/CVE-2022-50459.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50459"},{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"bcf3a2953d36bbfb9bd44ccb3db0897d935cc485"},{"fixed":"884a788f065578bb640382279a83d1df433b13e6"},{"fixed":"a26b0658751bb0a3b28386fca715333b104d32a2"},{"fixed":"897dbbc57d71e8a34ec1af8e573a142de457da38"},{"fixed":"0a0b861fce2657ba08ec356a74346b37ca4b2008"},{"fixed":"57569c37f0add1b6489e1a1563c71519daf732cf"}]},{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"0"},{"last_affected":"7d29e950766327f658cb92722b9445ac3b3ae023"}]}],"database_specific":{"source":"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2022-50459.json"}}],"schema_version":"1.7.5"}