Safeguard
Vulnerability Analysis•

CVE-2023-31029: Critical Stack Overflow in NVIDIA DGX A100 BMC

CVE-2023-31029 is a Critical (CVSS 9.3) stack overflow in the NVIDIA DGX A100 BMC host KVM daemon. Update BMC firmware to 00.22.05 or later to fix it.

Safeguard Security Team
3 min read

CVE-2023-31029 is a critical severity flaw (CVSS 9.3) in NVIDIA DGX A100 firmware. An unauthenticated attacker may cause a stack overflow in the host KVM daemon with a crafted network packet. NVIDIA's fix is BMC firmware 00.22.05 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.

Note on the vector: NVIDIA's bulletin and the record both give a local attack vector (AV:L) with a changed scope, even though the description mentions a network packet. Treat the 9.3 score as NVIDIA's rating and read the bulletin for context.

Two sibling entries, CVE-2023-31030 and CVE-2023-31024, describe similar problems in the same daemon.

How to check if you're exposed

Read the BMC firmware version in the BMC web interface under firmware information, or from the host with this command if ipmitool is installed:

sudo ipmitool mc info

The Firmware Revision line should be 00.22.05 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 BMC firmware 00.22.05 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 weakness types are CWE-121, stack based buffer overflow, and CWE-787, out of bounds write. NVIDIA says a successful exploit may lead to code execution, denial of service, information disclosure and data tampering.

Three KVM daemon memory bugs in one bulletin suggest that this service deserves the most attention. If you cannot update right away, keep the BMC off any network that untrusted systems can reach. The CVE is not on the CISA KEV list.

Management controllers deserve their own patch cadence. They are rarely covered by the operating system's update tools, and they often sit outside the scope of the teams who patch servers. Add the BMC firmware version to your inventory next to the operating system version, and review it after every NVIDIA firmware bulletin.

Quick check

Is this the same as CVE-2023-31030?

They are separate entries with near identical descriptions, fixed by the same firmware.

Why is the vector local?

The bulletin and record both list AV:L. They do not explain the difference from the description.

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.