Security readout for executives and security teams
Plain-English summary
CVE-2022-49335 is a Linux kernel AMDGPU driver crash issue. A local user can trigger a kernel NULL pointer dereference by submitting an invalid command stream with zero chunks, causing high availability impact. It is not described as remotely exploitable.
Executive priority
Treat as a moderate availability risk. Patch through normal kernel maintenance, faster for shared workstations, GPU compute hosts, or environments allowing untrusted local users.
Technical view
The flaw is CWE-476 in drm/amdgpu command submission handling. The kernel accepted a command submission with zero chunks, then later dereferenced missing state in amdgpu_cs_ioctl. The resolved behavior makes zero-chunk commands illegal.
Likely exposure
Exposure is likely limited to Linux systems using the AMDGPU DRM driver where a local user or process can access the relevant GPU interface. The CVSS vector requires local access and low privileges.
Exploitation context
The source bundle provides a crash trace from glxinfo with an incorrect userspace driver override. KEV is false, and no cited source states active exploitation in the wild.
Researcher notes
Evidence supports local denial of service through a malformed AMDGPU command submission. The bundle does not show confidentiality or integrity impact, remote reachability, public weaponization, or a non-patch workaround.
Mitigation direction
Apply vendor or distribution Linux kernel updates containing the referenced stable fixes.
Prioritize multi-user Linux systems with AMDGPU hardware or exposed GPU device access.
Check distro advisories for supported fixed package versions and backport status.
If patching is delayed, follow vendor guidance for temporary GPU access controls.
Validation and detection
Inventory Linux hosts using the AMDGPU DRM driver.
Confirm the running kernel includes a referenced stable commit or vendor backport.
Check package advisories for CVE-2022-49335 fixed status.
Review kernel logs for unexplained amdgpu_cs_ioctl oops events.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-476: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.