# CVE-2026-72088: scsi: hpsa: Fix DMA mapping leak on IOACCEL2 reset path

> A resource leak in the hpsa SCSI driver can lead to denial of service when IOACCEL2 reset paths are triggered.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-72088, DEBIAN-CVE-2026-72088, GHSA-pp64-c938-8878, UBUNTU-CVE-2026-72088

## What is CVE-2026-72088?

CVE-2026-72088 is a denial of service vulnerability in Linux, published on 15 Aug 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: hpsa: Fix DMA mapping leak on IOACCEL2 reset path

If phys_disk->in_reset is set, the function returns directly without
undoing the resources acquired for the command. Add the missing error
cleanup by unmapping the IOACCEL2 SG chain block when needed, unmapping
the SCSI command, and dropping the outstanding IOACCEL command count
before returning.

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


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

Apply the vendor's patch.

## Is CVE-2026-72088 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72088 is a denial of service vulnerability in Linux, published on 15 Aug 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-72088 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-72088/ (Markdown: https://insights.sbomify.com/CVE-2026-72088/index.md)
```

## Sources

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

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