CVE-2022-48792

scsi: pm8001: Fix use-after-free for aborted SSP/STP sas_task

HIGH
7.8
CVSS Score
Published: July 16, 2024 at 11:43 AM UTC
Updated: August 5, 2026 at 09:24 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: scsi: pm8001: Fix use-after-free for aborted SSP/STP sas_task Currently a use-after-free may occur if a sas_task is aborted by the upper layer before we handle the I/O completion in mpi_ssp_completion() or mpi_sata_completion(). In this case, the following are the two steps in handling those I/O completions: - Call complete() to inform the upper layer handler of completion of the I/O. - Release driver resources associated with the sas_task in pm8001_ccb_task_free() call. When complete() is called, the upper layer may free the sas_task. As such, we should not touch the associated sas_task afterwards, but we do so in the pm8001_ccb_task_free() call. Fix by swapping the complete() and pm8001_ccb_task_free() calls ordering.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 5.10.1024.15 ≤ v < 5.10.1024.15 ≤ v < 5.15.254.15 ≤ v < 5.16.114.15 ≤ v < 5.175.11 ≤ v < 5.15.255.16 ≤ v < 5.16.114.15869ddbdcae3b4fb83b99889abae31544c149b210
Vendor states this is fixed in d9d93f32534a0a80a1c26bdb0746d90a7b19c2c2 (fixed)
Vendor states this is fixed in df7abcaa1246e2537ab4016077b5443bb3c09378 (fixed)
Vendor states this is fixed in f61f9fccb2cb4bb275674a79d638704db6bc2171 (fixed)
Vendor states this is fixed in fe9ac3eaa2e387a5742b380b73a5a6bc237bf184 (fixed)
Vendor states this is fixed in 4.15 (unaffected)
Vendor states this is fixed in 5.10.102 (unaffected)
Vendor states this is fixed in 5.15.25 (unaffected)
Vendor states this is fixed in 5.16.11 (unaffected)
Vendor states this is fixed in 5.17 (unaffected)

References (4)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/d9d93f32534a0a80a1c26bdb0746d90a7b19c2c2
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/df7abcaa1246e2537ab4016077b5443bb3c09378
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/f61f9fccb2cb4bb275674a79d638704db6bc2171
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/fe9ac3eaa2e387a5742b380b73a5a6bc237bf184

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-416

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card