Home
» GitHub Advisories
» GHSA-2wv8-chjf-q56w
Description
An attacker could cooperatively pass data from one secure GPU process to another secure GPU process through shared secure memory allocations in the kernel module. Additionally, an attacker could disrupt the operation of another secure GPU process leading to image corruption / GPU hardware recovery.
Sharing secure memory allocations among various GPU secure processes allows an attacker to corrupt shared resource affecting other users.
Basic information
Type
unreviewed
Severity
medium Advisory on GitHub
Open advisory ↗ Repository advisory
—
Source code
Not specified Published (advisory)
2026-06-13 00:34:31 UTC
Updated
2026-06-15 21:31:34 UTC
NVD published
2026-06-12
EPSS Score
Score
Percentile
0.02%
5.19%
CVSS Scores
Base score
Version
Severity
Vector
5.5
3.1
—
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
CWEs
CWE id
Name
CWE-653
Improper Isolation or Compartmentalization
cvelogic
Threat Intelligence