CVE-2022-50818 (GCVE-0-2022-50818)
Vulnerability from cvelistv5 – Published: 2025-12-30 12:08 – Updated: 2025-12-30 12:08
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
References
Impacted products
| Vendor | Product | Version | ||
|---|---|---|---|---|
| Linux | Linux |
Affected:
2cbbf489778eb9dde51392ec5f74ae2868e4b857 , < 4e750e0d8e486569fcb7f4ba6f6471673ce7d8a2
(git)
Affected: 2cbbf489778eb9dde51392ec5f74ae2868e4b857 , < a62b9fc9775fbc8e666bb328f6e53c168054d6fe (git) Affected: 2cbbf489778eb9dde51392ec5f74ae2868e4b857 , < d8c22c4697c11ed28062afe3c2b377025be11a23 (git) |
||
{
"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": "2025-12-30T12:08:33.548Z",
"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": "2025-12-30T12:08:33.548Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"nvd": "{\"cve\":{\"id\":\"CVE-2022-50818\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-12-30T13:15:56.200\",\"lastModified\":\"2025-12-31T20:43:05.160\",\"vulnStatus\":\"Awaiting Analysis\",\"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().\"}],\"metrics\":{},\"references\":[{\"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\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
}
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
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.
Loading…
Loading…