Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2022-50520

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

Medium5.5EPSS 0.17%
Published
Updated
Reserved
Assigned by
Linux

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.

Scores

CVSS scores of CVE-2022-50520, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (6 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected c61e2775873f603148e8e998a938721b7d222d24 – < 6f28c7f67af4ef9bca580ab67ae2d4511797af56
    • affected c61e2775873f603148e8e998a938721b7d222d24 – < e738f82e5b1311e8fb3d1409491a6fcce6418fbe
    • affected c61e2775873f603148e8e998a938721b7d222d24 – < 1079df6acf56f99d86b0081a38c84701412cc90e
    • affected c61e2775873f603148e8e998a938721b7d222d24 – < 470a77989037c3ab2b08bf2d026d2c0ddc35ff5b
    • affected c61e2775873f603148e8e998a938721b7d222d24 – < 3991d98a8a07b71c02f3a39f77d6d9a7f575a5c4
    • affected c61e2775873f603148e8e998a938721b7d222d24 – < 88c6e0995c04b170563b5c894c50a3b2152e18c2
    • affected c61e2775873f603148e8e998a938721b7d222d24 – < b9decada8749b606fd8b4f04a3d6c74f7983d7bc
    • affected c61e2775873f603148e8e998a938721b7d222d24 – < a6cffe54064a5f6c2162a85af3c16c6b453eac4e
    • affected c61e2775873f603148e8e998a938721b7d222d24 – < 725a521a18734f65de05b8d353b5bd0d3ca4c37a
    • affected 61ebf0a926149cc161131470cf848cb70b3d6fe6
    • affected 0a1d9a860832a5ca43114cdebf0e8650463cc1f0
    • affected 5f54f145719f453dccc73304cd427096bf7b806c
    • affected 063ab9cb6308a0806d623c8d6dda5cb2b3b87fce
    • affected 3.2.29 – < 3.3
    • affected 3.4.12 – < 3.5
    • affected 3.5.5 – < 3.6
    • affected 3.2.60 – < 3.3
  • Linux · Linux

    • affected 3.6
    • unaffected < 3.6
    • unaffected 4.9.337 – ≤ 4.9.*
    • unaffected 4.14.303 – ≤ 4.14.*
    • unaffected 4.19.270 – ≤ 4.19.*
    • unaffected 5.4.229 – ≤ 5.4.*
    • unaffected 5.10.163 – ≤ 5.10.*
    • unaffected 5.15.86 – ≤ 5.15.*
    • unaffected 6.0.16 – ≤ 6.0.*
    • unaffected 6.1.2 – ≤ 6.1.*
    • unaffected 6.2 – ≤ *

References (9)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-50520 badge
[![CVE-2022-50520](https://trackcve.app/badge/CVE-2022-50520.svg)](https://trackcve.app/cve/CVE-2022-50520)

Record last updated .