scsi: iscsi: iscsi_tcp: Fix null-ptr-deref while calling getpeername()
In the Linux kernel, the following vulnerability has been resolved: scsi: iscsi: iscsi_tcp: Fix null-ptr-deref while calling getpeername() Fix a NULL pointer crash that occurs when we are freeing the socket at the same time we access it via sysfs. The problem is that: 1. iscsi_sw_tcp_conn_get_param() and iscsi_sw_tcp_host_get_param() take the frwd_lock and do sock_hold() then drop the frwd_lock. sock_hold() does a get on the "struct sock". 2. iscsi_sw_tcp_release_conn() does sockfd_put() which does the last put on the "struct socket" and that does __sock_release() which sets the sock->ops to NULL. 3. iscsi_sw_tcp_conn_get_param() and iscsi_sw_tcp_host_get_param() then call kernel_getpeername() which accesses the NULL sock->ops. Above we do a get on the "struct sock", but we needed a get on the "struct socket". Originally, we just held the frwd_lock the entire time but in commit bcf3a2953d36 ("scsi: iscsi: iscsi_tcp: Avoid holding spinlock while calling getpeername()") we switched to refcount based because the network layer changed and started taking a mutex in that path, so we could no longer hold the frwd_lock. Instead of trying to maintain multiple refcounts, this just has us use a mutex for accessing the socket in the interface code paths.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.10.150, 5.15.75, 5.19.17, 6.0.3
- CVEs
- CVE-2022-50459
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 8 Nov 2026, 00:45 UTC · Revision 1
Source evidence
scsi: iscsi: iscsi_tcp: Fix null-ptr-deref while calling getpeername()
core-osv · Original sourcePublished 1 Oct 2025, 11:45 UTC
In the Linux kernel, the following vulnerability has been resolved: scsi: iscsi: iscsi_tcp: Fix null-ptr-deref while calling getpeername() Fix a NULL pointer crash that occurs when we are freeing the socket at the same time we access it via sysfs. The problem is that: 1. iscsi_sw_tcp_conn_get_param() and iscsi_sw_tcp_host_get_param() take the frwd_lock and do sock_hold() then drop the frwd_lock. sock_hold() does a get on the "struct sock". 2. iscsi_sw_tcp_release_conn() does sockfd_put() which does the last put on the "struct socket" and that does __sock_release() which sets the sock->ops to NULL. 3. iscsi_sw_tcp_conn_get_param() and iscsi_sw_tcp_host_get_param() then call kernel_getpeername() which accesses the NULL sock->ops. Above we do a get on the "struct sock", but we needed a get on the "struct socket". Originally, we just held the frwd_lock the entire time but in commit bcf3a2953d36 ("scsi: iscsi: iscsi_tcp: Avoid holding spinlock while calling getpeername()") we switched to refcount based because the network layer changed and started taking a mutex in that path, so we could no longer hold the frwd_lock. Instead of trying to maintain multiple refcounts, this just has us use a mutex for accessing the socket in the interface code paths.
osv:CVE-2022-50459
Kernel
Fixed versions: 5.10.150, 5.15.75, 5.19.17, 6.0.3
Complete source record
{
"id": "ef50151d9ef6ce29c249f31c0b77c790b22235c78416c47d6cf85b2607dfeba5",
"url": "https://osv.dev/vulnerability/CVE-2022-50459",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "scsi: iscsi: iscsi_tcp: Fix null-ptr-deref while calling getpeername()",
"summary": "In the Linux kernel, the following vulnerability has been resolved: scsi: iscsi: iscsi_tcp: Fix null-ptr-deref while calling getpeername() Fix a NULL pointer crash that occurs when we are freeing the socket at the same time we access it via sysfs. The problem is that: 1. iscsi_sw_tcp_conn_get_param() and iscsi_sw_tcp_host_get_param() take the frwd_lock and do sock_hold() then drop the frwd_lock. sock_hold() does a get on the \"struct sock\". 2. iscsi_sw_tcp_release_conn() does sockfd_put() which does the last put on the \"struct socket\" and that does __sock_release() which sets the sock->ops to NULL. 3. iscsi_sw_tcp_conn_get_param() and iscsi_sw_tcp_host_get_param() then call kernel_getpeername() which accesses the NULL sock->ops. Above we do a get on the \"struct sock\", but we needed a get on the \"struct socket\". Originally, we just held the frwd_lock the entire time but in commit bcf3a2953d36 (\"scsi: iscsi: iscsi_tcp: Avoid holding spinlock while calling getpeername()\") we switched to refcount based because the network layer changed and started taking a mutex in that path, so we could no longer hold the frwd_lock. Instead of trying to maintain multiple refcounts, this just has us use a mutex for accessing the socket in the interface code paths.",
"evidence": "osv:CVE-2022-50459",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.10.150",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.75",
"evidence": "/affected/1/ranges"
},
{
"value": "5.19.17",
"evidence": "/affected/1/ranges"
},
{
"value": "6.0.3",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "CVE-2022-50459",
"aliases": [
"CVE-2022-50459"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "bcf3a2953d36bbfb9bd44ccb3db0897d935cc485"
},
{
"fixed": "884a788f065578bb640382279a83d1df433b13e6"
},
{
"fixed": "a26b0658751bb0a3b28386fca715333b104d32a2"
},
{
"fixed": "897dbbc57d71e8a34ec1af8e573a142de457da38"
},
{
"fixed": "0a0b861fce2657ba08ec356a74346b37ca4b2008"
},
{
"fixed": "57569c37f0add1b6489e1a1563c71519daf732cf"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "5.8.14"
},
{
"fixed": "5.9"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "7d29e950766327f658cb92722b9445ac3b3ae023"
}
]
}
],
"versions": [
"v5.8.18",
"v5.8.17",
"v5.8.16",
"v5.8.15",
"v5.8.14"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-50459.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.9.0"
},
{
"fixed": "5.10.150"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.75"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "5.19.17"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.20.0"
},
{
"fixed": "6.0.3"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-50459.json"
}
}
],
"modified": "2026-10-28T02:30:52.586984053Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/0a0b861fce2657ba08ec356a74346b37ca4b2008",
"https://git.kernel.org/stable/c/57569c37f0add1b6489e1a1563c71519daf732cf",
"https://git.kernel.org/stable/c/884a788f065578bb640382279a83d1df433b13e6",
"https://git.kernel.org/stable/c/897dbbc57d71e8a34ec1af8e573a142de457da38",
"https://git.kernel.org/stable/c/a26b0658751bb0a3b28386fca715333b104d32a2",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/50xxx/CVE-2022-50459.json",
"https://nvd.nist.gov/vuln/detail/CVE-2022-50459",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/50xxx/CVE-2022-50459.json"
}
},
"related_cves": [
{
"value": "CVE-2022-50459",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 521075,
"published_at": "2025-10-01T11:45:31.74+00:00"
}