# CVE-2026-23306: scsi: pm8001: Fix use-after-free in pm8001_queue_command()

> A use-after-free vulnerability in the Linux kernel's pm8001 SCSI driver allows local attackers to potentially execute code or escalate privileges via a double free scenario.

- **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:** 25 Mar 2026
- **Updated:** 5 Aug 2026
- **Also known as:** AZL-80604, BELL-CVE-2026-23306, DEBIAN-CVE-2026-23306, GHSA-m6g2-mpp7-vr6r, ROOT-OS-DEBIAN-12-CVE-2026-23306, ROOT-OS-DEBIAN-13-CVE-2026-23306, ROOT-OS-UBUNTU-2404-CVE-2026-23306, UBUNTU-CVE-2026-23306

## What is CVE-2026-23306?

CVE-2026-23306 is a high-severity use after free vulnerability in Linux kernel, published on 25 Mar 2026. 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 in pm8001_queue_command()

Commit e29c47fe8946 ("scsi: pm8001: Simplify pm8001_task_exec()") refactors
pm8001_queue_command(), however it introduces a potential cause of a double
free scenario when it changes the function to return -ENODEV in case of phy
down/device gone state.

In this path, pm8001_queue_command() updates task status and calls
task_done to indicate to upper layer that the task has been handled.
However, this also frees the underlying SAS task. A -ENODEV is then
returned to the caller. When libsas sas_ata_qc_issue() receives this error
value, it assumes the task wasn't handled/queued by LLDD and proceeds to
clean up and free the task again, resulting in a double free.

Since pm8001_queue_command() handles the SAS task in this case, it should
return 0 to the caller indicating that the task has been handled.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2026-23306?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-23306?

Apply the vendor's patch.

## Is CVE-2026-23306 being exploited?

There is no known exploitation of CVE-2026-23306 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-2026-23306 and fix it if it is affected.

What it is: CVE-2026-23306 is a high-severity use after free vulnerability in Linux kernel, published on 25 Mar 2026. 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-2026-23306 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-2026-23306/ (Markdown: https://insights.sbomify.com/CVE-2026-23306/index.md)
```

## Sources

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

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