Skip to content
NewA calmer, faster ZeroHour

NVIDIA GPU load/store units leak AES keys and stall colocated jobs

Original title: Dissecting the GPU Load/Store Unit and Exposing Its Security Risks

arXiv cs.CRby Wenbo Han ()1 min read1
AI summary · x-ai/grok-4.7Summaries by Vani AI

Bank conflicts or tag lookups alone recover a full AES-128 key, and covert-channel rates rise across GPU generations.

Researchers reverse-engineered how recent NVIDIA GPU load/store units serve loads, using microbenchmarks. They give a cycle-accurate latency formula and show loads contend on bank conflicts and L1 tag lookups. Through either channel they recover a full AES-128 key under a prior GPU AES timing-attack model. Under Multi-Process Service, both channels form cross-process covert channels, and pipeline starvation slowed colocated cuBLAS multiplication by up to 750x on the A100 and 563x on the H100.

Unconfirmed: Slowdown figures and channel rates are the authors' measurements, not independent reports.

Key facts
  • A full LSU pipeline can let one warp starve a warp from a later-launched block.
  • Covert channels use bank access or tag lookup across processes under MPS.
  • The reported cuBLAS slowdown is up to 750x on A100 and 563x on H100.
  • The authors say prior attacks covered only isolated LSU mechanisms.
Security assessment · AI, from the articlePublic proof of concept

Impact: AES-128 key recovery, covert channels, and colocated workload slowdown

ProductAffected
NVIDIA GPU load/store unitrecent NVIDIA GPUs, including A100 and H100
Analyze this story with Vani AIImpact, who is affected and what defenders should do, in a new chat

From the original article

1 min read at arxiv.org

GPUs are the main platform for large-scale machine learning and power the largest supercomputers. Their load/store units (LSUs) often determine kernel performance and have been exploited in prior attacks. Yet what is known about the LSU is only a few isolated mechanisms and parameters, and even a single one has been enough for an attack.

arXiv cs.CR

By Wenbo Han · arxiv.org

Read the full article at arXiv cs.CR

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.