CVE-2022-50542 [High] | Use-After-Free in Linux Kernel

In the Linux kernel, the following vulnerability has been resolved: media: si470x: Fix use-after-free in si470x_int_in_callback() syzbot reported use-after-free in si470x_int_in_callback() [1]. This indicates that urb->context, which contains struct si470x_device object, is freed when si470x_int_in_callback() is called. The cause of this issue is that si470x_int_in_callback() is called for freed urb. si470x_usb_driver_probe() calls si470x_start_usb(), which then calls usb_submit_urb() and si470x_start(). If si470x_start_usb() fails, si470x_usb_driver_probe() doesn't kill urb, but it just frees struct si470x_device object, as depicted below: si470x_usb_driver_probe() ... si470x_start_usb() ... usb_submit_urb() retval = si470x_start() return retval if (retval < 0) free struct si470x_device object, but don't kill urb This patch fixes this issue by killing urb when si470x_start_usb() fails and urb is submitted. If si470x_start_usb() fails and urb is not submitted, i.e. submitting usb fails, it just frees struct si470x_device object.

#	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
7.8	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	5.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

7.8

3.1

HIGH

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

5.9

[email protected]

OS Trackers for CVE-2022-50542

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2022-50542 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-50542
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2022-50542
`suse`	medium	—	https://www.suse.com/security/cve/CVE-2022-50542/
`ubuntu`	medium	CVE-2022-50542 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 80, needed 5, needs-triage 1.	https://ubuntu.com/security/CVE-2022-50542

Affected software / configurations for CVE-2022-50542

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

URL	Tags
https://git.kernel.org/stable/c/0ca298d548461d29615f9a2b1309e8dcf4a352c6	Patch
https://git.kernel.org/stable/c/146bd005ebb01ae190c22af050cb98623958c373	Patch
https://git.kernel.org/stable/c/1c6447d0fc68650e51586dde79b5090d9d77f13a	Patch
https://git.kernel.org/stable/c/52f54fe78cca24850a30865037250f63eb3d5bf7	Patch
https://git.kernel.org/stable/c/63648a7bd1a7599bcc2040a6d1792363ae4c2e1b	Patch
https://git.kernel.org/stable/c/6c8aee0c8fcc6dda94315f7908e8fa9bc75abe75	Patch
https://git.kernel.org/stable/c/7d21e0b1b41b21d628bf2afce777727bd4479aa5	Patch
https://git.kernel.org/stable/c/8c6151b8e8dd2d98ad2cd725d26d1e103d989891	Patch
https://git.kernel.org/stable/c/92b0888398e4ba51d93b618a6506781f4e3879c9	Patch

URL

CVE-2022-50542 | media: si470x: Fix use-after-free in si470x_int_in_callback()

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

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

Weakness enumeration for CVE-2022-50542

OS Trackers for CVE-2022-50542

Affected software / configurations for CVE-2022-50542

References for CVE-2022-50542