# CVE-2022-48791: scsi: pm8001: Fix use-after-free for aborted TMF sas_task

> A use-after-free vulnerability in the Linux kernel's pm8001 SCSI driver allows attackers to cause denial of service or potentially execute code via aborted TMF tasks.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Jul 2024
- **Updated:** 5 Aug 2026
- **Also known as:** DEBIAN-CVE-2022-48791, GHSA-hrwc-pg2q-pgc2, SUSE-SU-2024:3304-1, SUSE-SU-2025:1092-1, UBUNTU-CVE-2022-48791

## What is CVE-2022-48791?

CVE-2022-48791 is a high-severity use after free vulnerability in Linux kernel, published on 16 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

scsi: pm8001: Fix use-after-free for aborted TMF sas_task

Currently a use-after-free may occur if a TMF sas_task is aborted before we
handle the IO completion in mpi_ssp_completion(). The abort occurs due to
timeout.

When the timeout occurs, the SAS_TASK_STATE_ABORTED flag is set and the
sas_task is freed in pm8001_exec_internal_tmf_task().

However, if the I/O completion occurs later, the I/O completion still
thinks that the sas_task is available. Fix this by clearing the ccb->task
if the TMF times out - the I/O completion handler does nothing if this
pointer is cleared.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2022-48791?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kgraft-patch-SLE12-SP5_Update_60` | SUSE:Linux Enterprise Live Patching 12 SP5 | All versions | 6-2.1 |
| `kernel-rt` | SUSE:Linux Enterprise Micro 5.1 | All versions | 5.3.18-150300.184.1 |
| `kernel-source-rt` | SUSE:Linux Enterprise Micro 5.1 | All versions | 5.3.18-150300.184.1 |
| `kernel-rt` | SUSE:Linux Enterprise Micro 5.2 | All versions | 5.3.18-150300.184.1 |
| `kernel-source-rt` | SUSE:Linux Enterprise Micro 5.2 | All versions | 5.3.18-150300.184.1 |

Products: Linux kernel.

## How do I fix CVE-2022-48791?

Apply the vendor's patch.

## Is CVE-2022-48791 being exploited?

There is no known exploitation of CVE-2022-48791 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-48791 and fix it if it is affected.

What it is: CVE-2022-48791 is a high-severity use after free vulnerability in Linux kernel, published on 16 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-48791 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-48791/ (Markdown: https://insights.sbomify.com/CVE-2022-48791/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-48791
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-48791
- OSV: https://osv.dev/vulnerability/CVE-2022-48791

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-48791/
Summaries are generated and may contain mistakes; the official description above is the record.