CVE-2025-23247 [Medium] | Security Vulnerability in Cuda Toolkit

NVIDIA CUDA Toolkit for all platforms contains a vulnerability in the cuobjdump binary, where a failure to check the length of a buffer could allow a user to cause the tool to crash or execute arbitrary code by passing in a malformed ELF file. A successful exploit of this vulnerability might lead to arbitrary code execution.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-03-23	0.01%	0.07%	+0.06%
2	2025-05-28	—	0.01%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-03-23

0.01%

0.07%

+0.06%

2025-05-28

—

0.01%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
4.4	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N` 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:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:L) Some sensitive info could get out, but not a total data dump. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:N) Service keeps running; no real outage angle.	1.8	2.5	[email protected]
7.8	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. 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:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	5.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

4.4

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N 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:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L): Some sensitive info could get out, but not a total data dump.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N): Service keeps running; no real outage angle.

1.8

2.5

[email protected]

7.8

3.1

HIGH

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
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:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

5.9

[email protected]

OS Trackers for CVE-2025-23247

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2025-23247 not yet assigned priority: Debian including 1 source packages (nvidia-cuda-toolkit), 4 status rows across 4 suites (bookworm, bullseye, sid, trixie): open 4.	https://security-tracker.debian.org/tracker/CVE-2025-23247
`ubuntu`	medium	CVE-2025-23247 medium priority: Ubuntu including 1 source packages (nvidia-cuda-toolkit), 9 status rows across 9 suites (bionic, focal, jammy, noble, oracular, plucky, questing, upstream, xenial): needs-triage 7, ignored 2.	https://ubuntu.com/security/CVE-2025-23247

Affected software / configurations for CVE-2025-23247

Vendor	Product	Version	Raw CPE
nvidia	cuda_toolkit	< 12.9.0	cpe:2.3:a:nvidia:cuda_toolkit::::::::

References for CVE-2025-23247

URL	Tags
https://nvidia.custhelp.com/app/answers/detail/a_id/5643	Vendor Advisory
https://www.talosintelligence.com/vulnerability_reports/TALOS-2025-2151	Third Party Advisory

URL

CVE-2025-23247

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

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

Weakness enumeration for CVE-2025-23247

OS Trackers for CVE-2025-23247

Affected software / configurations for CVE-2025-23247

References for CVE-2025-23247