Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2022-50459

scsi: iscsi: iscsi_tcp: Fix null-ptr-deref while calling getpeername()

High7.8EPSS 0.18%
Published
Updated
Reserved
Assigned by
Linux

Description

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.

Scores

CVSS scores of CVE-2022-50459, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.18% · top 92% of all CVEs (6 Nov 2026)
Loading the EPSS history…

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

Weakness

Affected products

  • Linux · Linux

    • affected bcf3a2953d36bbfb9bd44ccb3db0897d935cc485 – < 884a788f065578bb640382279a83d1df433b13e6
    • affected bcf3a2953d36bbfb9bd44ccb3db0897d935cc485 – < a26b0658751bb0a3b28386fca715333b104d32a2
    • affected bcf3a2953d36bbfb9bd44ccb3db0897d935cc485 – < 897dbbc57d71e8a34ec1af8e573a142de457da38
    • affected bcf3a2953d36bbfb9bd44ccb3db0897d935cc485 – < 0a0b861fce2657ba08ec356a74346b37ca4b2008
    • affected bcf3a2953d36bbfb9bd44ccb3db0897d935cc485 – < 57569c37f0add1b6489e1a1563c71519daf732cf
    • affected 7d29e950766327f658cb92722b9445ac3b3ae023
    • affected 5.8.14 – < 5.9
  • Linux · Linux

    • affected 5.9
    • unaffected < 5.9
    • unaffected 5.10.150 – ≤ 5.10.*
    • unaffected 5.15.75 – ≤ 5.15.*
    • unaffected 5.19.17 – ≤ 5.19.*
    • unaffected 6.0.3 – ≤ 6.0.*
    • unaffected 6.1 – ≤ *

References (5)

Sources

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

Badge for a README or a ticket

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

Record last updated .