# CVE-2023-52515: RDMA/srp: Do not call scsi_done() from srp_abort()

> A use-after-free vulnerability in the Linux kernel's RDMA/SRP driver allows attackers to potentially execute code or cause a system crash.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Mar 2024
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2023-52515, DEBIAN-CVE-2023-52515, GHSA-9mhh-v2w9-x3xj, UBUNTU-CVE-2023-52515

## What is CVE-2023-52515?

CVE-2023-52515 is a critical use after free vulnerability in Linux kernel, published on 2 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

RDMA/srp: Do not call scsi_done() from srp_abort()

After scmd_eh_abort_handler() has called the SCSI LLD eh_abort_handler
callback, it performs one of the following actions:
* Call scsi_queue_insert().
* Call scsi_finish_command().
* Call scsi_eh_scmd_add().
Hence, SCSI abort handlers must not call scsi_done(). Otherwise all
the above actions would trigger a use-after-free. Hence remove the
scsi_done() call from srp_abort(). Keep the srp_free_req() call
before returning SUCCESS because we may not see the command again if
SUCCESS is returned.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2023-52515?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2023-52515?

Apply the vendor's patch.

## Is CVE-2023-52515 being exploited?

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

What it is: CVE-2023-52515 is a critical use after free vulnerability in Linux kernel, published on 2 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-52515 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-2023-52515/ (Markdown: https://insights.sbomify.com/CVE-2023-52515/index.md)
```

## Sources

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

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