CVE-2021-47652

video: fbdev: smscufx: Fix null-ptr-deref in ufx_usb_probe()

MEDIUM

5.5

CVSS Score

Published: February 26, 2025 at 01:54 AM UTC

Updated: June 17, 2026 at 04:18 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

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.3%

SSVC

No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: video: fbdev: smscufx: Fix null-ptr-deref in ufx_usb_probe() I got a null-ptr-deref report: BUG: kernel NULL pointer dereference, address: 0000000000000000 ... RIP: 0010:fb_destroy_modelist+0x38/0x100 ... Call Trace: ufx_usb_probe.cold+0x2b5/0xac1 [smscufx] usb_probe_interface+0x1aa/0x3c0 [usbcore] really_probe+0x167/0x460 ... ret_from_fork+0x1f/0x30 If fb_alloc_cmap() fails in ufx_usb_probe(), fb_destroy_modelist() will be called to destroy modelist in the error handling path. But modelist has not been initialized yet, so it will result in null-ptr-deref. Initialize modelist before calling fb_alloc_cmap() to fix this bug.

Affected

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

Linux Kernel · Linux

95%

3.2 ≤ v < 4.14.2763.2 ≤ v < 4.19.2383.2 ≤ v < 4.9.3113.2 ≤ v < 5.10.1103.2 ≤ v < 5.15.333.2 ≤ v < 5.16.193.2 ≤ v < 5.17.23.2 ≤ v < 5.183.2 ≤ v < 5.4.1894.10 ≤ v < 4.14.2764.15 ≤ v < 4.19.2384.20 ≤ v < 5.4.1895.11 ≤ v < 5.15.335.16 ≤ v < 5.16.195.17 ≤ v < 5.17.25.5 ≤ v < 5.10.1103.23c8a63e22a0802fd56380f6ab305b419f18eb6f5

Vendor states this is fixed in 0fd28daec73525382e5c992db8743bf76e42cd5c (fixed)

Vendor states this is fixed in 1791f487f877a9e83d81c8677bd3e7b259e7cb27 (fixed)

Vendor states this is fixed in 64ec3e678d76419f207b9cdd338dda438ca10b1c (fixed)

Vendor states this is fixed in 9280ef235b05e8f19f8bc6d547b992f0a0ef398d (fixed)

Vendor states this is fixed in c420b540db4b5d69de0a36d8b9d9a6a79a04f05a (fixed)

Vendor states this is fixed in d1b6a1f0c23b7164250479bf92e2893291dca539 (fixed)

Vendor states this is fixed in d396c651e2b508b6179bb678cc029f3becbf5170 (fixed)

Vendor states this is fixed in da8b269cc0a2526ebeaccbe2484c999eb0f822cf (fixed)

Vendor states this is fixed in dd3a6cc7385b89ec2303f39dfc3bafa4e24cec4b (fixed)

Vendor states this is fixed in 3.2 (unaffected)

Vendor states this is fixed in 4.14.276 (unaffected)

Vendor states this is fixed in 4.19.238 (unaffected)

Vendor states this is fixed in 4.9.311 (unaffected)

Vendor states this is fixed in 5.10.110 (unaffected)

Vendor states this is fixed in 5.15.33 (unaffected)

Vendor states this is fixed in 5.16.19 (unaffected)

Vendor states this is fixed in 5.17.2 (unaffected)

Vendor states this is fixed in 5.18 (unaffected)

Vendor states this is fixed in 5.4.189 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references