NVIDIA HGX / DGX (Hopper and Blackwell) - NVSwitch LS10 firmware: A misconfiguration of the LS10 NVSwitch lets an
Impact
A misconfiguration of the LS10 NVSwitch lets an attacker set an unsafe debug access level on the fabric switch itself. The NVSwitch is the component that enforces which GPU can address which peer over NVLink; anything that loosens its debug posture is a question mark over the multi-GPU partitioning that a shared HGX node depends on. Direct scored impact is denial of service with a changed scope.
Who can reach it
Local, low privileges, high complexity, from the host that manages the fabric. Fabric Manager runs here, so the practical prerequisite is code on the baseboard host - not inside a tenant VM.
What to do
Apply the NVSwitch firmware update from bulletin 5674 as part of the HGX firmware bundle. Cost: full node drain and power cycle across the whole baseboard; NVLink topology is re-established by Fabric Manager on restart, so verify fabric health and NVLink link counts after the flash before returning the node to the pool.
References
This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.