# CVE-2025-39778: objtool, nvmet: Fix out-of-bounds stack access in nvmet_ctrl_state_show()

> An out-of-bounds stack read in the Linux kernel's nvmet module can lead to information disclosure or system crashes.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:** 18 Apr 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2025-39778, DEBIAN-CVE-2025-39778, GHSA-2h4h-cj8f-67g5, UBUNTU-CVE-2025-39778

## What is CVE-2025-39778?

CVE-2025-39778 is a high-severity memory corruption vulnerability in Linux kernel, published on 18 Apr 2025. 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:

objtool, nvmet: Fix out-of-bounds stack access in nvmet_ctrl_state_show()

The csts_state_names[] array only has six sparse entries, but the
iteration code in nvmet_ctrl_state_show() iterates seven, resulting in a
potential out-of-bounds stack read.  Fix that.

Fixes the following warning with an UBSAN kernel:

  vmlinux.o: warning: objtool: .text.nvmet_ctrl_state_show: unexpected end of section

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2025-39778?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2025-39778?

Apply the vendor's patch.

## Is CVE-2025-39778 being exploited?

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

What it is: CVE-2025-39778 is a high-severity memory corruption vulnerability in Linux kernel, published on 18 Apr 2025. 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-2025-39778 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-2025-39778/ (Markdown: https://insights.sbomify.com/CVE-2025-39778/index.md)
```

## Sources

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

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