CVE-2022-49966: drm/amd/pm: add missing ->fini_microcode interface for Sienna Cichlid
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/pm: add missing ->fini_microcode interface for Sienna Cichlid
To avoid any potential memory leak.
Security readout for executives and security teams
Plain-English summary
This CVE covers a Linux kernel AMD graphics power-management cleanup issue. A missing microcode finalization interface for Sienna Cichlid could cause a potential memory leak. The public record does not provide CVSS, confirmed impact beyond leakage risk, or evidence of active exploitation.
Executive priority
Treat as routine kernel hygiene unless your estate has affected AMDGPU systems or vendor advisories raise severity. There is no sourced evidence here of exploitation or urgent internet-scale abuse, but kernel memory-management flaws should still be closed through standard patch cycles.
Technical view
The Linux kernel AMD DRM power-management code lacked a ->fini_microcode interface for Sienna Cichlid. Upstream stable commits resolve the issue to avoid a potential memory leak. The CVE record lists affected Linux kernel versions but does not describe privilege requirements, trigger conditions, or security boundary impact.
Likely exposure
Exposure appears limited to Linux kernels containing the affected AMD DRM/PM Sienna Cichlid code path. Organizations should prioritize systems with AMDGPU hardware and kernel versions identified in the CVE record, while confirming exact package status with their Linux distributor.
Exploitation context
The provided sources do not show KEV listing, active exploitation, public exploit availability, or weaponized use. Because the record only states a potential memory leak, operational risk depends on whether the affected driver path is present and reachable in deployed systems.
Researcher notes
The available record is sparse: no CVSS, CWE, exploitability detail, or trigger path is provided. Analysis should focus on commit diff review, vendor backport mapping, and whether the affected AMDGPU code path is compiled and used in target kernels.
Mitigation direction
Inventory Linux hosts with AMDGPU hardware and affected kernel versions.
Apply distributor kernel updates that include the referenced stable fixes.
If updates are unavailable, consult vendor guidance for supported mitigations.
Track kernel advisory updates for clarified severity or affected-version corrections.
Validation and detection
Check running kernel versions against the CVE affected-version data.
Confirm whether AMD DRM/PM Sienna Cichlid support is present on the host.
Verify installed kernel packages include the referenced upstream stable commits.
Monitor vendor advisories for backport identifiers and package-specific fixed versions.
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-2022-49966 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.
0CVSS vectors
3Timeline events
0ADP providers
5Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Jun 18, 2025, 11:00 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.