CVE-2022-50317 [Medium] | Security Vulnerability in Linux Kernel

In the Linux kernel, the following vulnerability has been resolved: drm/bridge: megachips: Fix a null pointer dereference bug When removing the module we will get the following warning: [ 31.911505] i2c-core: driver [stdp2690-ge-b850v3-fw] unregistered [ 31.912484] general protection fault, probably for non-canonical address 0xdffffc0000000001: 0000 [#1] PREEMPT SMP KASAN PTI [ 31.913338] KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f] [ 31.915280] RIP: 0010:drm_bridge_remove+0x97/0x130 [ 31.921825] Call Trace: [ 31.922533] stdp4028_ge_b850v3_fw_remove+0x34/0x60 [megachips_stdpxxxx_ge_b850v3_fw] [ 31.923139] i2c_device_remove+0x181/0x1f0 The two bridges (stdp2690, stdp4028) do not probe at the same time, so the driver does not call ge_b850v3_resgiter() when probing, causing the driver to try to remove the object that has not been initialized. Fix this by checking whether both the bridges are probed.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2025-09-16	—	0.02%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2025-09-16

—

0.02%

—

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-50317

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2022-50317 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-50317
`redhat`	low	—	https://access.redhat.com/security/cve/CVE-2022-50317
`suse`	medium	—	https://www.suse.com/security/cve/CVE-2022-50317/
`ubuntu`	medium	CVE-2022-50317 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 158, released 148, not-affected 90, needs-triage 1.	https://ubuntu.com/security/CVE-2022-50317

Affected software / configurations for CVE-2022-50317

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 4.14.263, < 4.14.296	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 4.19.226, < 4.19.262	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.4.174, < 5.4.220	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.10.94, < 5.10.150	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.15.17, < 5.15.75	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.16.3, < 5.19.17	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.0, < 6.0.3	cpe:2.3:o:linux:linux_kernel::::::::

References for CVE-2022-50317

URL	Tags
https://git.kernel.org/stable/c/1daf69228e310938177119c4eadcd30fc75c81e0	Patch
https://git.kernel.org/stable/c/1ff673333d46d2c1b053ebd0c1c7c7c79e36943e	Patch
https://git.kernel.org/stable/c/21764467ab396d9f08921e0a5ffa1214244e1ad9	Patch
https://git.kernel.org/stable/c/4610e7a4111fa3f3ce27c09d6d94008c55f1cd31	Patch
https://git.kernel.org/stable/c/5bc20bafcd87ba0858ab772cefc7047cb51bc249	Patch
https://git.kernel.org/stable/c/7371fad5cfe6eada6bb5523c895fd6074b15c2b9	Patch
https://git.kernel.org/stable/c/877e92e9b1bdeb580b31a46061005936be902cd4	Patch
https://git.kernel.org/stable/c/aaa512ad1e59f2edf8a9e4f2b167a44b24670679	Patch

URL

CVE-2022-50317 | drm/bridge: megachips: Fix a null pointer dereference bug

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

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

Weakness enumeration for CVE-2022-50317

OS Trackers for CVE-2022-50317

Affected software / configurations for CVE-2022-50317

References for CVE-2022-50317