In the Linux kernel, the following vulnerability has been resolved:
drm/amd/amdgpu: fix potential memleak
In function amdgpu_get_xgmi_hive, when kobject_init_and_add failed
There is a potential memleak if not call kobject_put.
Security readout for executives and security teams
Plain-English summary
This CVE is a Linux kernel AMDGPU driver bug that can leak memory when an internal kernel object setup fails. The public record does not provide a severity score, exploit evidence, or business-impact details. Treat it as a kernel hygiene issue for affected Linux systems, especially where AMDGPU support is enabled.
Executive priority
Handle through routine kernel patch management unless affected AMD GPU systems are business-critical or difficult to reboot. There is no source-backed evidence of active exploitation, but kernel memory leaks can affect reliability and should not remain indefinitely unpatched.
Technical view
The issue is in drm/amd/amdgpu, specifically amdgpu_get_xgmi_hive. If kobject_init_and_add fails, the code could miss kobject_put, creating a potential memory leak. The record says the vulnerability is resolved in Linux stable commits, but does not describe privilege requirements, trigger reliability, or impact beyond memory leakage.
Likely exposure
Exposure appears limited to Linux systems running affected kernel versions with the AMDGPU driver code present. The bundle names Linux kernel versions including 5.10, 5.10.84, 5.15.7, and 5.16, but downstream package mapping needs vendor confirmation.
Exploitation context
No active exploitation is cited. The CVE is not marked KEV, and the provided sources do not describe public exploit activity, exploitation prerequisites, or weaponized use. Evidence supports only a potential memory leak condition in kernel driver error handling.
Researcher notes
The record is sparse: no CVSS, CWE, exploit notes, or detailed affected-version ranges are provided. Analysis should stay tied to the upstream Linux fix and distribution backports. Validate by code review or vendor package metadata rather than assuming all kernels in a major branch are affected.
Mitigation direction
Update affected Linux kernels to builds containing the referenced stable fixes.
Check your Linux distribution or appliance vendor advisory for exact fixed package versions.
Prioritize systems using AMDGPU functionality or AMD GPU-capable kernel builds.
Do not deploy directly from upstream commits without normal vendor validation.
Validation and detection
Inventory Linux kernel versions across servers, workstations, and GPU-enabled systems.
Identify hosts where AMDGPU driver support is installed or enabled.
Map installed kernel packages to vendor-fixed releases or listed stable commits.
Confirm the amdgpu_get_xgmi_hive cleanup path includes kobject_put on failure.
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.
cve · low confidence lookup
CVE-2021-47550 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.