GPUCC-MIG-01: MIG partitions do not share the confidential GPU¶
| Property | Value |
|---|---|
| Severity | high |
| Platform | NVIDIA GPU Confidential Computing |
| Lifecycle stage | runtime |
| Trust boundary | memory |
| Assurance | report-derived |
| Mode | Passive: reads only the files and values you pass to the scan. |
What it checks¶
It passes when:
- MIG is off now and after the next reset; the confidential GPU is not partitioned.
How to fix¶
- Disable MIG (nvidia-smi -mig 0), reset the GPU so the pending mode is also disabled, then re-attest before releasing keys or loading weights.
- Disable MIG, reset the GPU, and re-attest before releasing keys.
After the fix, scan again: the check should report PASS.
When it is not assessed¶
SKIP:
- No --gpu-attestation-report specified; skipping check.
- The attestation report has no 'mig' block (current and pending MIG mode); MIG co-tenancy is unassessed.
ERROR:
- Could not read/parse attestation report: …
Scan inputs¶
The untrust scan options this check reads:
| Option | Description |
|---|---|
--gpu-attestation-report |
Path to a captured NVIDIA GPU attestation report (JSON). |
Permissions¶
None. The check reads only the files or values you pass to the scan.
Related¶
- Runtime detection
DET-G3(NVIDIA GPU CC): MIG partitioning appeared on the confidential GPU
Generated from untrust 1.3.0 (commit 7ef462d9a0c3).