CVE-2022-50275: drm/radeon: Add the missed acpi_put_table() to fix memory leak
In the Linux kernel, the following vulnerability has been resolved:
drm/radeon: Add the missed acpi_put_table() to fix memory leak
When the radeon driver reads the bios information from ACPI
table in radeon_acpi_vfct_bios(), it misses to call acpi_put_table()
to release the ACPI memory after the init, so add acpi_put_table()
properly to fix the memory leak.
v2: fix text formatting (Alex)
Security readout for executives and security teams
Plain-English summary
This CVE is a Linux kernel Radeon graphics driver memory leak. When the driver reads BIOS information from an ACPI table, it failed to release that table afterward. The sources do not provide CVSS, exploit evidence, or business-impact detail, so treat this as maintenance-risk kernel exposure rather than an emergency.
Executive priority
Handle through normal kernel patch management. Escalate only for fleets with broad Radeon-equipped Linux exposure, constrained patch windows, or repeated memory-pressure incidents tied to graphics initialization.
Technical view
The issue is in drm/radeon, specifically radeon_acpi_vfct_bios(). The function reads BIOS data from the ACPI VFCT table but missed acpi_put_table(), leaving ACPI table memory unreleased after initialization. Kernel stable commits add the missing release call.
Likely exposure
Exposure is most likely on Linux systems using affected kernels with the Radeon driver and ACPI VFCT BIOS path. The bundle lists Linux as affected and references multiple stable kernel fixes, but does not identify distributions, hardware models, or CPEs.
Exploitation context
The provided sources do not show active exploitation, public exploit activity, or KEV listing. The described condition is a memory leak during Radeon ACPI BIOS handling, with no source evidence of privilege escalation, remote access, or code execution.
Researcher notes
Evidence is limited to the CVE record description and Linux stable commit references. No CVSS, CWE, exploit status, CPEs, or distribution-specific fixes are included in the bundle, so validation should rely on kernel commit presence and vendor package guidance.
Mitigation direction
Update to a vendor kernel containing the referenced stable fixes.
Prioritize systems using AMD Radeon graphics on affected Linux kernels.
Follow Linux distribution advisories for package-specific fixed versions.
Avoid direct deployment workarounds unless provided by the kernel or distribution vendor.
Validation and detection
Inventory Linux kernel versions and Radeon driver usage across endpoints and servers.
Check distribution advisories for CVE-2022-50275 fixed package status.
Confirm deployed kernels include one of the referenced stable commits or downstream equivalent.
Review fleet logs for Radeon initialization issues only as supporting context.
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-50275 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
9Source 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.
Sep 15, 2025, 14:21 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.