Local service interruption via unsafe debug configuration
Published Sep 4, 2025 · Updated Sep 4, 2025
Improper debug-access control in the NVIDIA HGX and DGX LS10 component allows local users to interrupt service via misconfiguration. The LS10 configuration accepts an unsafe debug access level instead of enforcing the intended restriction; NVIDIA does not identify the setting or code path. Exploitation requires local low-privileged access and high-complexity conditions; NVIDIA reports denial of service and limited integrity impact but does not disclose whether interruption is a crash, hang, or reboot.
Summary
What happened
Improper debug-access control in the NVIDIA HGX and DGX LS10 component allows local users to interrupt service via misconfiguration. The LS10 configuration accepts an unsafe debug access level instead of enforcing the intended restriction; NVIDIA does not identify the setting or code path. Exploitation requires local low-privileged access and high-complexity conditions; NVIDIA reports denial of service and limited integrity impact but does not disclose whether interruption is a crash, hang, or reboot.
The record
- CVE
- CVE-2025-23302
- Published
- Sep 4, 2025
- Updated
- Sep 4, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-1244, CAPEC-114, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 4, 2025CVE publishedPublication date reported by the CVE source.
- Sep 4, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo