CVE-2025-39778: objtool, nvmet: Fix out-of-bounds stack access in nvmet_ctrl_state_show()
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
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue is a local memory safety bug in the NVMe target code. A low-privileged local user may be able to read unintended stack memory or disrupt availability on affected systems. It is important for shared Linux hosts and systems exposing NVMe target functionality.
Executive priority
Treat as high priority for Linux fleets with shared local access or NVMe target use. It is not supported as internet-exploited from the provided evidence, but confidentiality and availability impacts justify timely patching.
Technical view
nvmet_ctrl_state_show() iterates past the sparse csts_state_names[] array, causing a potential out-of-bounds stack read. The CVE maps this to CWE-125 with local attack vector, low complexity, low privileges, high confidentiality impact, and high availability impact.
Likely exposure
Exposure is limited to affected Linux kernel builds, especially systems using or enabling the NVMe target subsystem. The provided version data is incomplete and should be validated against vendor kernel advisories and the referenced upstream stable fixes.
Exploitation context
The source bundle does not show CISA KEV listing or any cited evidence of active exploitation. CVSS indicates exploitation requires local access with low privileges and no user interaction. No remote exploitation evidence is provided.
Researcher notes
The strongest evidence is the upstream Linux fix description and CVSS vector. Affected version data in the bundle is sparse and duplicated, so precise exposure requires vendor package mapping. Avoid assuming exploit availability or broader product impact.
Mitigation direction
Apply vendor kernel updates containing the referenced stable Linux fixes.
Check distribution advisories for exact fixed kernel package versions.
Prioritize shared hosts and systems with NVMe target functionality enabled.
Restrict unnecessary local user access until patched.
Follow vendor guidance if backported fixes use different version numbers.
Validation and detection
Inventory Linux kernel versions across affected hosts.
Identify systems using or loading NVMe target functionality.
Compare installed kernels with vendor advisories and referenced stable commits.
Confirm patched kernels are booted, not only installed.
Monitor vendor security notes for corrected affected-version ranges.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-125: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-125 · source CWE mapping
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.