CVE-2025-39778 [High] | Out-of-bounds Read in Linux Kernel

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

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-05-27	0.07%	0.04%	-0.03%
2	2026-02-12	0.02%	0.07%	+0.05%
3	2025-04-18	—	0.02%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-05-27

0.07%

0.04%

-0.03%

2026-02-12

0.02%

0.07%

+0.05%

2025-04-18

—

0.02%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
7.1	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	5.2	[email protected]
7.1	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	5.2	134c704f-9b21-4f2e-91b3-4a467353bcc0

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

7.1

3.1

HIGH

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

5.2

[email protected]

7.1

3.1

HIGH

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

5.2

134c704f-9b21-4f2e-91b3-4a467353bcc0

OS Trackers for CVE-2025-39778

vendor	priority	summary	link
`debian`	unimportant	CVE-2025-39778 unimportant priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2025-39778
`redhat`	high	—	https://access.redhat.com/security/cve/CVE-2025-39778
`suse`	medium	CVE-2025-39778 severity moderate: SUSE including 52 source package names (cluster-md-kmp-default, dlm-kmp-default, …), 267 product×package rows across 45 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS, … (45 product lines)): Known Not Affected 241, Fixed 26.	https://www.suse.com/security/cve/CVE-2025-39778/
`ubuntu`	medium	CVE-2025-39778 medium priority: Ubuntu including 158 source packages (linux, linux-allwinner-5.19, …), 1550 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 1144, ignored 147, not-affected 142, released 115, needs-triage 2.	https://ubuntu.com/security/CVE-2025-39778

Affected software / configurations for CVE-2025-39778

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 6.11, < 6.12.23	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.13, < 6.13.11	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.14, < 6.14.2	cpe:2.3:o:linux:linux_kernel::::::::

References for CVE-2025-39778

URL	Tags
https://git.kernel.org/stable/c/0cc0efc58d6c741b2868d4af24874d7fec28a575	Patch
https://git.kernel.org/stable/c/107a23185d990e3df6638d9a84c835f963fe30a6	Patch
https://git.kernel.org/stable/c/1adc93a525fdee8e2b311e6d5fd93eb69714ca05	Patch
https://git.kernel.org/stable/c/8fbf37a3577b4d64c150cafde338eee17b2f2ea4	Patch

URL

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

Exploit prediction scoring system (EPSS) score for CVE-2025-39778

Common vulnerability scoring system (CVSS) metrics for CVE-2025-39778

Weakness enumeration for CVE-2025-39778

OS Trackers for CVE-2025-39778

Affected software / configurations for CVE-2025-39778

References for CVE-2025-39778