CVE-2022-50542

media: si470x: Fix use-after-free in si470x_int_in_callback()

HIGH
7.8
CVSS Score
Published: October 7, 2025 at 03:21 PM UTC
Updated: June 17, 2026 at 05:23 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.6 ≤ v < 4.14.3033.6 ≤ v < 4.19.2703.6 ≤ v < 4.9.3373.6 ≤ v < 5.10.1633.6 ≤ v < 5.15.863.6 ≤ v < 5.4.2293.6 ≤ v < 6.0.163.6 ≤ v < 6.1.23.6 ≤ v < 6.24.10 ≤ v < 4.14.3034.15 ≤ v < 4.19.2704.20 ≤ v < 5.4.2295.11 ≤ v < 5.15.865.16 ≤ v < 6.0.165.5 ≤ v < 5.10.1636.1 ≤ v < 6.1.23.6779471110c6f0f7f7c223fc696170ec750ac3531
Vendor states this is fixed in 0ca298d548461d29615f9a2b1309e8dcf4a352c6 (fixed)
Vendor states this is fixed in 146bd005ebb01ae190c22af050cb98623958c373 (fixed)
Vendor states this is fixed in 1c6447d0fc68650e51586dde79b5090d9d77f13a (fixed)
Vendor states this is fixed in 52f54fe78cca24850a30865037250f63eb3d5bf7 (fixed)
Vendor states this is fixed in 63648a7bd1a7599bcc2040a6d1792363ae4c2e1b (fixed)
Vendor states this is fixed in 6c8aee0c8fcc6dda94315f7908e8fa9bc75abe75 (fixed)
Vendor states this is fixed in 7d21e0b1b41b21d628bf2afce777727bd4479aa5 (fixed)
Vendor states this is fixed in 8c6151b8e8dd2d98ad2cd725d26d1e103d989891 (fixed)
Vendor states this is fixed in 92b0888398e4ba51d93b618a6506781f4e3879c9 (fixed)
Vendor states this is fixed in 3.6 (unaffected)
Vendor states this is fixed in 4.14.303 (unaffected)
Vendor states this is fixed in 4.19.270 (unaffected)
Vendor states this is fixed in 4.9.337 (unaffected)
Vendor states this is fixed in 5.10.163 (unaffected)
Vendor states this is fixed in 5.15.86 (unaffected)
Vendor states this is fixed in 5.4.229 (unaffected)
Vendor states this is fixed in 6.0.16 (unaffected)
Vendor states this is fixed in 6.1.2 (unaffected)
Vendor states this is fixed in 6.2 (unaffected)

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-416

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card