CVE-2022-49365: drm/amdgpu: Off by one in dm_dmub_outbox1_low_irq()
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu: Off by one in dm_dmub_outbox1_low_irq()
The > ARRAY_SIZE() should be >= ARRAY_SIZE() to prevent an out of bounds
access.
Security readout for executives and security teams
Plain-English summary
CVE-2022-49365 is a Linux kernel AMDGPU driver flaw caused by an off-by-one bounds check. A local, low-privileged user could trigger an out-of-bounds access that may crash or disrupt the system. The cited CVSS impact is availability only, with no confidentiality or integrity impact stated.
Executive priority
Treat as a moderate patching item. It can affect availability on relevant Linux AMDGPU systems, but the provided evidence does not support remote exploitation, data theft, or known active exploitation.
Technical view
The issue is in drm/amdgpu dm_dmub_outbox1_low_irq(), where a comparison used > ARRAY_SIZE() instead of >= ARRAY_SIZE(), allowing an out-of-bounds access. The CVE maps to CWE-193 and CVSS 3.1 score 5.5: local, low complexity, low privileges, no user interaction, high availability impact.
Likely exposure
Exposure is most likely on Linux systems running affected kernel builds with the AMDGPU DRM driver in use. The source bundle lists Linux kernel versions and commit identifiers, but does not provide distribution-specific package names or a complete deployment matrix.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation evidence. The CVSS vector indicates exploitation requires local access and low privileges, so this is mainly a local denial-of-service risk rather than a remote compromise risk.
Researcher notes
Evidence is limited to the CVE record and kernel stable commits. The affected-version data in the bundle is not distribution-specific, so validation should rely on distro package advisories and commit backport confirmation rather than version strings alone.
Mitigation direction
Update to a vendor-supported kernel containing the referenced stable fixes.
Check Linux distribution advisories for the exact fixed package version.
Prioritize shared GPU workstations and multi-user Linux systems.
Restrict untrusted local shell access where timely patching is delayed.
Validation and detection
Inventory Linux hosts using AMD GPUs or the amdgpu driver.
Compare kernel versions against vendor advisories and fixed package metadata.
Check kernel changelogs for the referenced stable commit IDs.
Confirm patched hosts rebooted into the updated kernel.
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-193: 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.