CVE-2022-50818 (GCVE-0-2022-50818)

Vulnerability from cvelistv5 – Published: 2025-12-30 12:08 – Updated: 2026-05-11 19:25
VLAI
Title
scsi: pm8001: Fix running_req for internal abort commands
Summary
In the Linux kernel, the following vulnerability has been resolved: scsi: pm8001: Fix running_req for internal abort commands Disabling the remote phy for a SATA disk causes a hang: root@(none)$ more /sys/class/sas_phy/phy-0:0:8/target_port_protocols sata root@(none)$ echo 0 > sys/class/sas_phy/phy-0:0:8/enable root@(none)$ [ 67.855950] sas: ex 500e004aaaaaaa1f phy08 change count has changed [ 67.920585] sd 0:0:2:0: [sdc] Synchronizing SCSI cache [ 67.925780] sd 0:0:2:0: [sdc] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=DRIVER_OK [ 67.935094] sd 0:0:2:0: [sdc] Stopping disk [ 67.939305] sd 0:0:2:0: [sdc] Start/Stop Unit failed: Result: hostbyte=0x04 driverbyte=DRIVER_OK ... [ 123.998998] INFO: task kworker/u192:1:642 blocked for more than 30 seconds. [ 124.005960] Not tainted 6.0.0-rc1-205202-gf26f8f761e83 #218 [ 124.012049] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 124.019872] task:kworker/u192:1 state:D stack:0 pid: 642 ppid: 2 flags:0x00000008 [ 124.028223] Workqueue: 0000:04:00.0_event_q sas_port_event_worker [ 124.034319] Call trace: [ 124.036758] __switch_to+0x128/0x278 [ 124.040333] __schedule+0x434/0xa58 [ 124.043820] schedule+0x94/0x138 [ 124.047045] schedule_timeout+0x2fc/0x368 [ 124.051052] wait_for_completion+0xdc/0x200 [ 124.055234] __flush_workqueue+0x1a8/0x708 [ 124.059328] sas_porte_broadcast_rcvd+0xa8/0xc0 [ 124.063858] sas_port_event_worker+0x60/0x98 [ 124.068126] process_one_work+0x3f8/0x660 [ 124.072134] worker_thread+0x70/0x700 [ 124.075793] kthread+0x1a4/0x1b8 [ 124.079014] ret_from_fork+0x10/0x20 The issue is that the per-device running_req read in pm8001_dev_gone_notify() never goes to zero and we never make progress. This is caused by missing accounting for running_req for when an internal abort command completes. In commit 2cbbf489778e ("scsi: pm8001: Use libsas internal abort support") we started to send internal abort commands as a proper sas_task. In this when we deliver a sas_task to HW the per-device running_req is incremented in pm8001_queue_command(). However it is never decremented for internal abort commnds, so decrement in pm8001_mpi_task_abort_resp().
Severity
No CVSS data available.
Assigner
Linux CNA under the mitre root
CNA scorecard D 53/100 over 6638 records in the last 180 days details
References
Impacted products
Vendor Product Version CPE status
Linux Linux Affected: 2cbbf489778eb9dde51392ec5f74ae2868e4b857 , < 4e750e0d8e486569fcb7f4ba6f6471673ce7d8a2 (git)
Affected: 2cbbf489778eb9dde51392ec5f74ae2868e4b857 , < a62b9fc9775fbc8e666bb328f6e53c168054d6fe (git)
Affected: 2cbbf489778eb9dde51392ec5f74ae2868e4b857 , < d8c22c4697c11ed28062afe3c2b377025be11a23 (git)
guessed Create a notification for this product.
Linux Linux Affected: 5.18
Unaffected: 0 , < 5.18 (semver)
Unaffected: 5.19.17 , ≤ 5.19.* (semver)
Unaffected: 6.0.3 , ≤ 6.0.* (semver)
Unaffected: 6.1 , ≤ * (original_commit_for_fix)
guessed Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/scsi/pm8001/pm8001_hwi.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "4e750e0d8e486569fcb7f4ba6f6471673ce7d8a2",
              "status": "affected",
              "version": "2cbbf489778eb9dde51392ec5f74ae2868e4b857",
              "versionType": "git"
            },
            {
              "lessThan": "a62b9fc9775fbc8e666bb328f6e53c168054d6fe",
              "status": "affected",
              "version": "2cbbf489778eb9dde51392ec5f74ae2868e4b857",
              "versionType": "git"
            },
            {
              "lessThan": "d8c22c4697c11ed28062afe3c2b377025be11a23",
              "status": "affected",
              "version": "2cbbf489778eb9dde51392ec5f74ae2868e4b857",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/scsi/pm8001/pm8001_hwi.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.18"
            },
            {
              "lessThan": "5.18",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.19.*",
              "status": "unaffected",
              "version": "5.19.17",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.0.*",
              "status": "unaffected",
              "version": "6.0.3",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.1",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.19.17",
                  "versionStartIncluding": "5.18",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.0.3",
                  "versionStartIncluding": "5.18",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.1",
                  "versionStartIncluding": "5.18",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: pm8001: Fix running_req for internal abort commands\n\nDisabling the remote phy for a SATA disk causes a hang:\n\nroot@(none)$ more /sys/class/sas_phy/phy-0:0:8/target_port_protocols\nsata\nroot@(none)$ echo 0 \u003e sys/class/sas_phy/phy-0:0:8/enable\nroot@(none)$ [   67.855950] sas: ex 500e004aaaaaaa1f phy08 change count has changed\n[   67.920585] sd 0:0:2:0: [sdc] Synchronizing SCSI cache\n[   67.925780] sd 0:0:2:0: [sdc] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=DRIVER_OK\n[   67.935094] sd 0:0:2:0: [sdc] Stopping disk\n[   67.939305] sd 0:0:2:0: [sdc] Start/Stop Unit failed: Result: hostbyte=0x04 driverbyte=DRIVER_OK\n...\n[  123.998998] INFO: task kworker/u192:1:642 blocked for more than 30 seconds.\n[  124.005960]   Not tainted 6.0.0-rc1-205202-gf26f8f761e83 #218\n[  124.012049] \"echo 0 \u003e /proc/sys/kernel/hung_task_timeout_secs\" disables this message.\n[  124.019872] task:kworker/u192:1  state:D stack:0 pid:  642 ppid: 2 flags:0x00000008\n[  124.028223] Workqueue: 0000:04:00.0_event_q sas_port_event_worker\n[  124.034319] Call trace:\n[  124.036758]  __switch_to+0x128/0x278\n[  124.040333]  __schedule+0x434/0xa58\n[  124.043820]  schedule+0x94/0x138\n[  124.047045]  schedule_timeout+0x2fc/0x368\n[  124.051052]  wait_for_completion+0xdc/0x200\n[  124.055234]  __flush_workqueue+0x1a8/0x708\n[  124.059328]  sas_porte_broadcast_rcvd+0xa8/0xc0\n[  124.063858]  sas_port_event_worker+0x60/0x98\n[  124.068126]  process_one_work+0x3f8/0x660\n[  124.072134]  worker_thread+0x70/0x700\n[  124.075793]  kthread+0x1a4/0x1b8\n[  124.079014]  ret_from_fork+0x10/0x20\n\nThe issue is that the per-device running_req read in\npm8001_dev_gone_notify() never goes to zero and we never make progress.\nThis is caused by missing accounting for running_req for when an internal\nabort command completes.\n\nIn commit 2cbbf489778e (\"scsi: pm8001: Use libsas internal abort support\")\nwe started to send internal abort commands as a proper sas_task. In this\nwhen we deliver a sas_task to HW the per-device running_req is incremented\nin pm8001_queue_command(). However it is never decremented for internal\nabort commnds, so decrement in pm8001_mpi_task_abort_resp()."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-05-11T19:25:42.709Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/4e750e0d8e486569fcb7f4ba6f6471673ce7d8a2"
        },
        {
          "url": "https://git.kernel.org/stable/c/a62b9fc9775fbc8e666bb328f6e53c168054d6fe"
        },
        {
          "url": "https://git.kernel.org/stable/c/d8c22c4697c11ed28062afe3c2b377025be11a23"
        }
      ],
      "title": "scsi: pm8001: Fix running_req for internal abort commands",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2022-50818",
    "datePublished": "2025-12-30T12:08:33.548Z",
    "dateReserved": "2025-12-30T12:06:07.131Z",
    "dateUpdated": "2026-05-11T19:25:42.709Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2022-50818",
      "date": "2026-11-15",
      "epss": "0.00242",
      "percentile": "0.1542"
    },
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "defaultStatus": "unaffected",
                "product": "Linux",
                "programFiles": [
                  "drivers/scsi/pm8001/pm8001_hwi.c"
                ],
                "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
                "vendor": "Linux",
                "versions": [
                  {
                    "lessThan": "4e750e0d8e486569fcb7f4ba6f6471673ce7d8a2",
                    "status": "affected",
                    "version": "2cbbf489778eb9dde51392ec5f74ae2868e4b857",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "a62b9fc9775fbc8e666bb328f6e53c168054d6fe",
                    "status": "affected",
                    "version": "2cbbf489778eb9dde51392ec5f74ae2868e4b857",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "d8c22c4697c11ed28062afe3c2b377025be11a23",
                    "status": "affected",
                    "version": "2cbbf489778eb9dde51392ec5f74ae2868e4b857",
                    "versionType": "git"
                  }
                ]
              },
              {
                "defaultStatus": "affected",
                "product": "Linux",
                "programFiles": [
                  "drivers/scsi/pm8001/pm8001_hwi.c"
                ],
                "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
                "vendor": "Linux",
                "versions": [
                  {
                    "status": "affected",
                    "version": "5.18"
                  },
                  {
                    "lessThan": "5.18",
                    "status": "unaffected",
                    "version": "0",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "5.19.*",
                    "status": "unaffected",
                    "version": "5.19.17",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "6.0.*",
                    "status": "unaffected",
                    "version": "6.0.3",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "*",
                    "status": "unaffected",
                    "version": "6.1",
                    "versionType": "original_commit_for_fix"
                  }
                ]
              }
            ],
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: pm8001: Fix running_req for internal abort commands\n\nDisabling the remote phy for a SATA disk causes a hang:\n\nroot@(none)$ more /sys/class/sas_phy/phy-0:0:8/target_port_protocols\nsata\nroot@(none)$ echo 0 \u003e sys/class/sas_phy/phy-0:0:8/enable\nroot@(none)$ [   67.855950] sas: ex 500e004aaaaaaa1f phy08 change count has changed\n[   67.920585] sd 0:0:2:0: [sdc] Synchronizing SCSI cache\n[   67.925780] sd 0:0:2:0: [sdc] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=DRIVER_OK\n[   67.935094] sd 0:0:2:0: [sdc] Stopping disk\n[   67.939305] sd 0:0:2:0: [sdc] Start/Stop Unit failed: Result: hostbyte=0x04 driverbyte=DRIVER_OK\n...\n[  123.998998] INFO: task kworker/u192:1:642 blocked for more than 30 seconds.\n[  124.005960]   Not tainted 6.0.0-rc1-205202-gf26f8f761e83 #218\n[  124.012049] \"echo 0 \u003e /proc/sys/kernel/hung_task_timeout_secs\" disables this message.\n[  124.019872] task:kworker/u192:1  state:D stack:0 pid:  642 ppid: 2 flags:0x00000008\n[  124.028223] Workqueue: 0000:04:00.0_event_q sas_port_event_worker\n[  124.034319] Call trace:\n[  124.036758]  __switch_to+0x128/0x278\n[  124.040333]  __schedule+0x434/0xa58\n[  124.043820]  schedule+0x94/0x138\n[  124.047045]  schedule_timeout+0x2fc/0x368\n[  124.051052]  wait_for_completion+0xdc/0x200\n[  124.055234]  __flush_workqueue+0x1a8/0x708\n[  124.059328]  sas_porte_broadcast_rcvd+0xa8/0xc0\n[  124.063858]  sas_port_event_worker+0x60/0x98\n[  124.068126]  process_one_work+0x3f8/0x660\n[  124.072134]  worker_thread+0x70/0x700\n[  124.075793]  kthread+0x1a4/0x1b8\n[  124.079014]  ret_from_fork+0x10/0x20\n\nThe issue is that the per-device running_req read in\npm8001_dev_gone_notify() never goes to zero and we never make progress.\nThis is caused by missing accounting for running_req for when an internal\nabort command completes.\n\nIn commit 2cbbf489778e (\"scsi: pm8001: Use libsas internal abort support\")\nwe started to send internal abort commands as a proper sas_task. In this\nwhen we deliver a sas_task to HW the per-device running_req is incremented\nin pm8001_queue_command(). However it is never decremented for internal\nabort commnds, so decrement in pm8001_mpi_task_abort_resp()."
          }
        ],
        "id": "CVE-2022-50818",
        "lastModified": "2026-06-17T05:24:14.520",
        "metrics": {},
        "published": "2025-12-30T13:15:56.200",
        "references": [
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/4e750e0d8e486569fcb7f4ba6f6471673ce7d8a2"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/a62b9fc9775fbc8e666bb328f6e53c168054d6fe"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/d8c22c4697c11ed28062afe3c2b377025be11a23"
          }
        ],
        "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "vulnStatus": "Deferred"
      }
    },
    "redhat_vex": {
      "aggregate_severity": "Low",
      "current_release_date": "2026-11-07T11:05:42+00:00",
      "cve": "CVE-2022-50818",
      "id": "CVE-2022-50818",
      "initial_release_date": "2022-01-01T00:00:00+00:00",
      "product_status:known_affected": "14",
      "product_status:known_not_affected": "186",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: scsi: pm8001: Fix running_req for internal abort commands",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2022/cve-2022-50818.json",
      "version": "3"
    },
    "suse_vex": {
      "aggregate_severity": "moderate",
      "current_release_date": "2026-11-01T03:00:51Z",
      "cve": "CVE-2022-50818",
      "id": "CVE-2022-50818",
      "initial_release_date": "2025-12-31T00:32:03Z",
      "product_status:known_affected": "374",
      "product_status:known_not_affected": "490",
      "product_status:recommended": "87",
      "source": "SUSE CSAF VEX",
      "status": "interim",
      "title": "SUSE CVE CVE-2022-50818",
      "url": "https://ftp.suse.com/pub/projects/security/csaf-vex/2025/cve-2022-50818.json",
      "version": "26"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.