# CVE-2026-90007: scsi: pm8001: Use rollback index when freeing MSI-X vectors

> A logic error in the pm8001 SCSI driver causes incorrect IRQ freeing during initialization failure, potentially leading to resource leaks or system instability.

- **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 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-101250, BELL-CVE-2026-90007, DEBIAN-CVE-2026-90007, GHSA-jq5h-3g7m-2crv, UBUNTU-CVE-2026-90007

## What is CVE-2026-90007?

CVE-2026-90007 is a high-severity vulnerability in Linux, published on 16 Sep 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: Use rollback index when freeing MSI-X vectors

pm8001_request_msix() unwinds previously registered handlers with
free_irq() when request_irq() fails. The rollback loop uses the failing
index i for every iteration instead of the already registered vector
index j.

That passes the wrong IRQ/dev_id pair to free_irq() and leaves the
earlier handlers installed. Use j for both pci_irq_vector() and the
matching irq_vector entry in the rollback loop.

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


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

Apply the vendor's patch.

## Is CVE-2026-90007 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-90007 and fix it if it is affected.

What it is: CVE-2026-90007 is a high-severity vulnerability in Linux, published on 16 Sep 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-90007 in the wild and no public exploit code.

Affected product: Linux. 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-90007/ (Markdown: https://insights.sbomify.com/CVE-2026-90007/index.md)
```

## Sources

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

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