Safeguard
Vulnerability Analysis•

CVE-2023-31035: High SMI Callout Flaw in NVIDIA DGX A100 SBIOS

CVE-2023-31035 is a High (CVSS 7.5) SMI callout flaw in the NVIDIA DGX A100 SBIOS that could run code at SMM level. Update SBIOS to 1.25 or later.

Safeguard Security Team
3 min read

CVE-2023-31035 is a high severity flaw (CVSS 7.5) in NVIDIA DGX A100 firmware. An attacker may use an SMI callout to run arbitrary code at the SMM level. NVIDIA's fix is SBIOS 1.25 or later, delivered in the firmware update container 23.12.1.

What's affected

NVIDIA's bulletin (revision 1.2, 25 January 2024) lists these fixed versions, delivered through the NVIDIA DGX A100 Firmware Update Container version 23.12.1 on the NVIDIA Enterprise Support Portal.

  • BMC: all versions prior to 00.22.05 are affected. Fixed: 00.22.05.
  • SBIOS: all versions prior to 1.25 are affected. Fixed: 1.25.

The vector is local, high complexity, high privileges, with a changed scope.

How to check if you're exposed

Read the SBIOS version from the host:

sudo dmidecode -s bios-version

The fixed SBIOS is 1.25 or later. This is a device or appliance issue, not a package you pull from a registry, so a dependency scan will not see it. Safeguard's free in-browser scan at https://gold.safeguard.sh/scan reads dependency manifests and will not detect firmware running on hardware. Use your asset inventory instead.

What to do now

  1. Find every NVIDIA DGX A100 system and record its BMC and SBIOS versions.
  2. Update to SBIOS 1.25 or later by installing the DGX A100 Firmware Update Container 23.12.1 from the NVIDIA Enterprise Support Portal.
  3. Keep BMC interfaces on a separate management network that only administrators can reach.

Why it matters

The record lists CWE-20, improper input validation. SMM, system management mode, is a highly privileged processor mode used by firmware, and code running there is invisible to the operating system. An SMI callout is a call from that firmware into code outside its protected memory, which is a known risk area.

NVIDIA lists code execution, denial of service, privilege escalation and information disclosure as impacts. High privilege and complexity requirements keep it at 7.5, but if exploited it could survive operating system reinstalls. The CVE is not on the CISA KEV list.

System management mode bugs are hard to detect after the fact, because the code runs below the operating system. Defenders usually rely on firmware updates and on boot integrity measurements where available. Keep a record of the SBIOS version on every system so you can show it is at 1.25 or later. Where your hardware supports it, check whether secure boot and firmware measurement features are turned on, since they help detect unexpected changes to firmware.

Quick check

What is SMM?

System management mode, a privileged processor mode used by firmware.

What fixes it?

SBIOS 1.25 or later.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.