# GSD-2023-1001608: scsi: hpsa: Fix possible memory leak in hpsa_add_sas_device()

> A memory leak in the hpsa SCSI driver could allow an attacker to cause a denial of service by exhausting kernel memory.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 17 Jan 2023

## What is GSD-2023-1001608?

GSD-2023-1001608 is a memory corruption vulnerability in Kernel, published on 17 Jan 2023. 

### Official description

scsi: hpsa: Fix possible memory leak in hpsa_add_sas_device()

This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v4.9.337 by commit 07e97ce1a239595f8b0bb5cfd368f586de4a2a5a, it was introduced in version v4.4 by commit d04e62b9d63a7498735761dc40eaed88b7fd9d80. For more details please see the references link.

## Which versions are affected by GSD-2023-1001608?

1 open source package ship an affected version, including Kernel.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Kernel` | Linux | All versions | None |

## How do I fix GSD-2023-1001608?

No fix has been published for GSD-2023-1001608 yet. Limit exposure of the affected software until one is available.

## Is GSD-2023-1001608 being exploited?

There is no known exploitation of GSD-2023-1001608 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GSD-2023-1001608 and fix it if it is affected.

What it is: GSD-2023-1001608 is a memory corruption vulnerability in Kernel, published on 17 Jan 2023. 
Exploitation: There is no known exploitation of GSD-2023-1001608 in the wild and no public exploit code.

Affected packages and fixed versions:
- Kernel (Linux): affected all versions; no fix listed

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/GSD-2023-1001608/ (Markdown: https://insights.sbomify.com/GSD-2023-1001608/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GSD-2023-1001608

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