Firmware code execution via NULL pointer dereference
Published Aug 25, 2026 · Updated Aug 26, 2026
NULL pointer dereference in NVIDIA DGX Spark UEFI 1.110.12 and earlier allows local users to execute code and interrupt service. NVIDIA identifies the locus only as system firmware and has not disclosed which pointer is left null or what firmware input reaches the dereference. Administrative local access and no user interaction are required; successful exploitation can cross the firmware boundary to alter or disclose data, execute code, or interrupt service.
Summary
What happened
NULL pointer dereference in NVIDIA DGX Spark UEFI 1.110.12 and earlier allows local users to execute code and interrupt service. NVIDIA identifies the locus only as system firmware and has not disclosed which pointer is left null or what firmware input reaches the dereference. Administrative local access and no user interaction are required; successful exploitation can cross the firmware boundary to alter or disclose data, execute code, or interrupt service.
The record
- CVE
- CVE-2026-24263
- Published
- Aug 25, 2026
- Updated
- Aug 26, 2026
- Vendor
- DPDK Project
- Product
- DGX Spark
- Classifications
- CWE-476, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Aug 25, 2026CVE publishedPublication date reported by the CVE source.
- Aug 26, 2026Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 to 1.110.12
What conditions does exploitation require?
What is affected?
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