CVE-2022-50520

drm/radeon: Fix PCI device refcount leak in radeon_atrm_get_bios()

MEDIUM
5.5
CVSS Score
Published: October 7, 2025 at 03:19 PM UTC
Updated: June 17, 2026 at 05:23 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: drm/radeon: Fix PCI device refcount leak in radeon_atrm_get_bios() As comment of pci_get_class() says, it returns a pci_device with its refcount increased and decreased the refcount for the input parameter @from if it is not NULL. If we break the loop in radeon_atrm_get_bios() with 'pdev' not NULL, we need to call pci_dev_put() to decrease the refcount. Add the missing pci_dev_put() to avoid refcount leak.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 3.2.29v ≥ 3.2.60v ≥ 3.4.12v ≥ 3.5.53.2.29 ≤ v < 3.33.2.60 ≤ v < 3.33.4.12 ≤ v < 3.53.5.5 ≤ v < 3.63.6 ≤ v < 4.14.3033.6 ≤ v < 4.19.2703.6 ≤ v < 4.9.3373.6 ≤ v < 5.10.1633.6 ≤ v < 5.15.863.6 ≤ v < 5.4.2293.6 ≤ v < 6.0.163.6 ≤ v < 6.1.23.6 ≤ v < 6.23.6.1 ≤ v < 4.9.3374.10 ≤ v < 4.14.3034.15 ≤ v < 4.19.2704.20 ≤ v < 5.4.2295.11 ≤ v < 5.15.865.16 ≤ v < 6.0.165.5 ≤ v < 5.10.1636.1 ≤ v < 6.1.20a1d9a860832a5ca43114cdebf0e8650463cc1f03.2.293.2.603.4.123.5.53.63.6 rc33.6 rc43.6 rc53.6 rc63.6 rc75f54f145719f453dccc73304cd427096bf7b806c61ebf0a926149cc161131470cf848cb70b3d6fe663ab9cb6308a806d623c8d6dda5cb2b3b87fcec61e2775873f603148e8e998a938721b7d222d24
Vendor states this is fixed in 1079df6acf56f99d86b0081a38c84701412cc90e (fixed)
Vendor states this is fixed in 3991d98a8a07b71c02f3a39f77d6d9a7f575a5c4 (fixed)
Vendor states this is fixed in 470a77989037c3ab2b08bf2d026d2c0ddc35ff5b (fixed)
Vendor states this is fixed in 6f28c7f67af4ef9bca580ab67ae2d4511797af56 (fixed)
Vendor states this is fixed in 725a521a18734f65de05b8d353b5bd0d3ca4c37a (fixed)
Vendor states this is fixed in 88c6e0995c04b170563b5c894c50a3b2152e18c2 (fixed)
Vendor states this is fixed in a6cffe54064a5f6c2162a85af3c16c6b453eac4e (fixed)
Vendor states this is fixed in b9decada8749b606fd8b4f04a3d6c74f7983d7bc (fixed)
Vendor states this is fixed in e738f82e5b1311e8fb3d1409491a6fcce6418fbe (fixed)
Affected range stops below 3.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 3.6 (unaffected)
Vendor states this is fixed in 4.14.303 (unaffected)
Vendor states this is fixed in 4.19.270 (unaffected)
Vendor states this is fixed in 4.9.337 (unaffected)
Vendor states this is fixed in 5.10.163 (unaffected)
Vendor states this is fixed in 5.15.86 (unaffected)
Vendor states this is fixed in 5.4.229 (unaffected)
Vendor states this is fixed in 6.0.16 (unaffected)
Vendor states this is fixed in 6.1.2 (unaffected)
Vendor states this is fixed in 6.2 (unaffected)

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
NVD-CWE-Other

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card