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

In the Linux kernel, the following vulnerability has been resolved: media: solo6x10: fix possible memory leak in solo_sysfs_init() If device_register() returns error in solo_sysfs_init(), the name allocated by dev_set_name() need be freed. As comment of device_register() says, it should use put_device() to give up the reference in the error path. So fix this by calling put_device(), then the name can be freed in kobject_cleanup().

#	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-50547

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2022-50547 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-50547
`redhat`	—	—	https://access.redhat.com/security/cve/CVE-2022-50547
`suse`	medium	CVE-2022-50547 severity moderate: SUSE including 26 source package names (cluster-md-kmp-default, dlm-kmp-default, …), 272 product×package rows across 54 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Linux Enterprise High Availability Extension 15 SP7, … (54 product lines)): Known Not Affected 272.	https://www.suse.com/security/cve/CVE-2022-50547/
`ubuntu`	medium	CVE-2022-50547 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-50547

Affected software / configurations for CVE-2022-50547

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 3.10, < 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::::::::

References for CVE-2022-50547

URL	Tags
https://git.kernel.org/stable/c/49060c0da57a381563e482e331dc9d4c3725b41b	Patch
https://git.kernel.org/stable/c/7b02c50d3978840781808e13bc13137fb81286b5	Patch
https://git.kernel.org/stable/c/7cf71bbe5d2ee12613f6e278888f5fc9c5c0cc2b	Patch
https://git.kernel.org/stable/c/7f5866dd96d95b74e439f6ee17b8abd8195179fb	Patch
https://git.kernel.org/stable/c/83d4b1ae98a47a739fa5241300b86eb1110d5d63	Patch
https://git.kernel.org/stable/c/9416861170ba0da8ddb0f4fd2d28334f0ed3b9c2	Patch
https://git.kernel.org/stable/c/963729538674be4cb8fa292529ecf32de0d6c6dd	Patch
https://git.kernel.org/stable/c/b61509093e1af69e336a094d439b8e1137cb40d8	Patch
https://git.kernel.org/stable/c/d6db105bcfbdbbbd484e788a0ddf8140a4a8c486	Patch

URL

CVE-2022-50547 | media: solo6x10: fix possible memory leak in solo_sysfs_init()

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

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

Weakness enumeration for CVE-2022-50547

OS Trackers for CVE-2022-50547

Affected software / configurations for CVE-2022-50547

References for CVE-2022-50547