LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-48792 is a Linux kernel bug in the pm8001 storage driver. Under specific aborted SAS/SATA task handling, the driver may use memory after it has been freed. The public record does not provide CVSS, impact, or active exploitation evidence, so urgency depends on whether affected kernels and this driver are present.

Executive priority

Treat this as a targeted kernel maintenance issue, not a confirmed emergency. Prioritize storage-heavy Linux servers and appliances first, especially where downtime from kernel faults would be costly. Escalate if vendor advisories add severity, exploitability, or active exploitation evidence.

Technical view

The flaw is a use-after-free in mpi_ssp_completion() or mpi_sata_completion(). complete() can let the upper layer free the sas_task, but pm8001_ccb_task_free() then still touches task-associated state. The kernel fix swaps that cleanup/completion ordering. Sources list affected Linux kernel versions and stable commit references, but no CWE or CVSS.

Likely exposure

Exposure is most likely on Linux systems running affected kernel versions with the pm8001 SCSI/SAS storage driver in use. General Linux estates may not be exposed if the driver or relevant hardware path is absent. Distribution backports may change version-only assessments.

Exploitation context

The source bundle does not cite active exploitation, and KEV status is false. The trigger context involves aborted SSP/STP sas_task handling before I/O completion processing. Public sources here do not establish remote reachability, privilege requirements, or reliable exploitation outcomes.

Researcher notes

The key code issue is post-completion access to sas_task-associated resources after the upper layer may free the task. The fix is ordering-based, not a new control. Evidence is incomplete on practical impact, reachable attack surface, and affected distribution packages.

Mitigation direction

  • Apply kernel updates containing the referenced stable fixes.
  • Check your Linux distribution advisory for backported fixes.
  • Prioritize systems using the pm8001 storage driver.
  • If patching is blocked, request vendor-supported temporary guidance.

Validation and detection

  • Inventory Linux kernel versions against the affected version data.
  • Identify hosts where the pm8001 driver is loaded or required.
  • Confirm patched kernels include the cited stable commits or vendor backports.
  • Document any systems deferred from patching and their business owner.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-48792 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux869ddbdcae3b4fb83b99889abae31544c149b210, 869ddbdcae3b4fb83b99889abae31544c149b210, 869ddbdcae3b4fb83b99889abae31544c149b210, 869ddbdcae3b4fb83b99889abae31544c149b210unaffected
LinuxLinux4.15, 0, 5.10.102, 5.15.25, 5.16.11, 5.17affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.