Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Apple | M1 Pro |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.416% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Apple
Apple m1 Pro |
|
| Vendors & Products |
Apple
Apple m1 Pro |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Apple M1 GPU Register Leakage Enables Secret Recovery Across Sandboxed Apps |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Apple M1 GPU Register Leakage Enables Secret Recovery Across Sandboxed Apps |
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-200 | |
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Apple M1 GPUs retain register file data between compute shader dispatches from different processes. A sandboxed Metal attacker app can run a GPU reader shader that reads stale register values left by a separate sandboxed victim app. In the proof of concept, GPUVictim.app generates a fresh random 128-bit secret using SecRandomCopyBytes and loads it into GPU registers. GPUAttacker.app, a separate sandboxed app, recovers the exact secret from stale GPU register state. NOTE: The vendor stated that this behavior affects only legacy hardware and has already been addressed at the hardware level in current-generation Apple Silicon. | |
| References |
|