# Interpret NVIDIA extension driverVersion according to the VM family

> Does the Linux NVIDIA extension's driverVersion setting always name the installed GPU driver?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-533-interpret-nvidia-extension-driverversion-according-to-the-vm-family/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:23:03+00:00
- Modified: 2026-09-10T02:11:18+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, IT
- Reading time: 2 minutes

## What you need to know

Does the Linux NVIDIA extension's driverVersion setting always name the installed GPU driver?

## Potentially affected

Operators using the NVIDIA GPU Driver Extension on a currently supported Linux N-series configuration.

## DSE recommendation

Label the requested Toolkit or GRID version explicitly in the deployment record.

## Article

## Source facts

The Linux NVIDIA extension’s general settings table maps driverVersion to a GRID driver on NV VMs and a CUDA Toolkit version on NC/ND VMs. Known-issues guidance separately prescribes installGridNC=True and driverVersion=595.58.03 for NC_RTXPRO6000BSE_v6. For the selected CUDA version, the extension installs the latest corresponding drivers. Installed GPU drivers do not subsequently update automatically through this extension. Installation can reboot the VM, and the extension does not support Secure Boot. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/virtual-machines/extensions/hpccompute-gpu-linux).

## Applicability

Use this check when reviewing an existing extension deployment or preparing a driver change on a supported OS and VM family. Confirm the current support matrix, family-specific known issues, and installation method first; do not apply a familiar version string across families without checking what it selects.

## DSE recommendation

Label the requested Toolkit or GRID version explicitly in the deployment record. Have the workload owner distinguish the requested setting from the driver and Toolkit actually required by the application. Plan an explicit driver-maintenance procedure and an appropriate disruption window. If Secure Boot is required, review the documented manual-installation path instead of treating the extension as eligible.

## Verification

Inspect the submitted extension settings, installed driver, and Toolkit where applicable. Compare them with the application’s supported combination and run its representative GPU task. Save sanitized version evidence and the observed restart behavior. Do not close a driver-update change merely because the extension resource remains installed or its provisioning state is successful.

## Official references

[Microsoft Learn: NVIDIA GPU Driver Extension for Linux](https://learn.microsoft.com/en-us/azure/virtual-machines/extensions/hpccompute-gpu-linux). Source reviewed September 9, 2026.

## Primary reference

- Name: NVIDIA GPU Driver Extension - Azure Linux VMs - Azure Virtual Machines | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/virtual-machines/extensions/hpccompute-gpu-linux
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Interpret NVIDIA extension driverVersion according to the VM family,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-533-interpret-nvidia-extension-driverversion-according-to-the-vm-family/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.