CVE-2022-50520 [Medium] | Information Disclosure in Linux Kernel

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.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2025-10-08	—	0.03%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2025-10-08

—

0.03%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
5.5	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	3.6	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

5.5

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

3.6

[email protected]

OS Trackers for CVE-2022-50520

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2022-50520 not yet assigned priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2022-50520
`redhat`	low	—	https://access.redhat.com/security/cve/CVE-2022-50520
`suse`	medium	—	https://www.suse.com/security/cve/CVE-2022-50520/
`ubuntu`	medium	CVE-2022-50520 medium priority: Ubuntu including 158 source packages (linux, linux-allwinner-5.19, …), 1414 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): DNE 1017, ignored 161, released 150, not-affected 81, needed 4, needs-triage 1.	https://ubuntu.com/security/CVE-2022-50520

Affected software / configurations for CVE-2022-50520

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 3.2.29, < 3.3	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 3.2.60, < 3.3	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 3.4.12, < 3.5	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 3.5.5, < 3.6	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 3.6.1, < 4.9.337	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 4.10, < 4.14.303	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 4.15, < 4.19.270	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 4.20, < 5.4.229	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.5, < 5.10.163	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.11, < 5.15.86	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.16, < 6.0.16	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.1, < 6.1.2	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	3.6	cpe:2.3:o:linux:linux_kernel:3.6:-::::::
linux	linux_kernel	3.6	cpe:2.3:o:linux:linux_kernel:3.6:rc3::::::
linux	linux_kernel	3.6	cpe:2.3:o:linux:linux_kernel:3.6:rc4::::::
linux	linux_kernel	3.6	cpe:2.3:o:linux:linux_kernel:3.6:rc5::::::
linux	linux_kernel	3.6	cpe:2.3:o:linux:linux_kernel:3.6:rc6::::::
linux	linux_kernel	3.6	cpe:2.3:o:linux:linux_kernel:3.6:rc7::::::

References for CVE-2022-50520

URL	Tags
https://git.kernel.org/stable/c/1079df6acf56f99d86b0081a38c84701412cc90e	Patch
https://git.kernel.org/stable/c/3991d98a8a07b71c02f3a39f77d6d9a7f575a5c4	Patch
https://git.kernel.org/stable/c/470a77989037c3ab2b08bf2d026d2c0ddc35ff5b	Patch
https://git.kernel.org/stable/c/6f28c7f67af4ef9bca580ab67ae2d4511797af56	Patch
https://git.kernel.org/stable/c/725a521a18734f65de05b8d353b5bd0d3ca4c37a	Patch
https://git.kernel.org/stable/c/88c6e0995c04b170563b5c894c50a3b2152e18c2	Patch
https://git.kernel.org/stable/c/a6cffe54064a5f6c2162a85af3c16c6b453eac4e	Patch
https://git.kernel.org/stable/c/b9decada8749b606fd8b4f04a3d6c74f7983d7bc	Patch
https://git.kernel.org/stable/c/e738f82e5b1311e8fb3d1409491a6fcce6418fbe	Patch

URL

CVE-2022-50520 | drm/radeon: Fix PCI device refcount leak in radeon_atrm_get_bios()

Exploit prediction scoring system (EPSS) score for CVE-2022-50520

Common vulnerability scoring system (CVSS) metrics for CVE-2022-50520

Weakness enumeration for CVE-2022-50520

OS Trackers for CVE-2022-50520

Affected software / configurations for CVE-2022-50520

References for CVE-2022-50520