GPUCC-MEMHYG-01: CVM memory hygiene: core dumps, swap, and ptrace cannot leak staged secrets¶
| Property | Value |
|---|---|
| Severity | high |
| Platform | NVIDIA GPU Confidential Computing |
| Lifecycle stage | runtime |
| Trust boundary | memory |
| Assurance | operator-declared |
| Mode | Passive: reads only the files and values you pass to the scan. |
What it checks¶
It passes when:
- Core dumps disabled, swap disabled/encrypted, and ptrace restricted.
How to fix¶
- Disable core dumps (RLIMIT_CORE 0 / coredump.conf), disable or encrypt swap, and restrict ptrace (yama ptrace_scope) on the CVM so the plaintext weights/DEK staged in RAM cannot be captured via dump, swap, or ptrace.
After the fix, scan again: the check should report PASS.
When it is not assessed¶
SKIP:
- No --gpu-kbs-policy specified; skipping check.
ERROR:
- Could not read/parse key-release policy: …
Scan inputs¶
The untrust scan options this check reads:
| Option | Description |
|---|---|
--gpu-kbs-policy |
Key-release policy JSON: attest-before-ready, decrypt location. |
Permissions¶
None. The check reads only the files or values you pass to the scan.
Generated from untrust 1.3.0 (commit 7ef462d9a0c3).