CVE-2022-49741

fbdev: smscufx: fix error handling code in ufx_usb_probe

MEDIUM
5.5
CVSS Score
Published: March 27, 2025 at 04:42 PM UTC
Updated: June 17, 2026 at 05:19 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
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: fbdev: smscufx: fix error handling code in ufx_usb_probe The current error handling code in ufx_usb_probe have many unmatching issues, e.g., missing ufx_free_usb_list, destroy_modedb label should only include framebuffer_release, fb_dealloc_cmap only matches fb_alloc_cmap. My local syzkaller reports a memory leak bug: memory leak in ufx_usb_probe BUG: memory leak unreferenced object 0xffff88802f879580 (size 128): comm "kworker/0:7", pid 17416, jiffies 4295067474 (age 46.710s) hex dump (first 32 bytes): 80 21 7c 2e 80 88 ff ff 18 d0 d0 0c 80 88 ff ff .!|............. 00 d0 d0 0c 80 88 ff ff e0 ff ff ff 0f 00 00 00 ................ backtrace: [<ffffffff814c99a0>] kmalloc_trace+0x20/0x90 mm/slab_common.c:1045 [<ffffffff824d219c>] kmalloc include/linux/slab.h:553 [inline] [<ffffffff824d219c>] kzalloc include/linux/slab.h:689 [inline] [<ffffffff824d219c>] ufx_alloc_urb_list drivers/video/fbdev/smscufx.c:1873 [inline] [<ffffffff824d219c>] ufx_usb_probe+0x11c/0x15a0 drivers/video/fbdev/smscufx.c:1655 [<ffffffff82d17927>] usb_probe_interface+0x177/0x370 drivers/usb/core/driver.c:396 [<ffffffff82712f0d>] call_driver_probe drivers/base/dd.c:560 [inline] [<ffffffff82712f0d>] really_probe+0x12d/0x390 drivers/base/dd.c:639 [<ffffffff8271322f>] __driver_probe_device+0xbf/0x140 drivers/base/dd.c:778 [<ffffffff827132da>] driver_probe_device+0x2a/0x120 drivers/base/dd.c:808 [<ffffffff82713c27>] __device_attach_driver+0xf7/0x150 drivers/base/dd.c:936 [<ffffffff82710137>] bus_for_each_drv+0xb7/0x100 drivers/base/bus.c:427 [<ffffffff827136b5>] __device_attach+0x105/0x2d0 drivers/base/dd.c:1008 [<ffffffff82711d36>] bus_probe_device+0xc6/0xe0 drivers/base/bus.c:487 [<ffffffff8270e242>] device_add+0x642/0xdc0 drivers/base/core.c:3517 [<ffffffff82d14d5f>] usb_set_configuration+0x8ef/0xb80 drivers/usb/core/message.c:2170 [<ffffffff82d2576c>] usb_generic_driver_probe+0x8c/0xc0 drivers/usb/core/generic.c:238 [<ffffffff82d16ffc>] usb_probe_device+0x5c/0x140 drivers/usb/core/driver.c:293 [<ffffffff82712f0d>] call_driver_probe drivers/base/dd.c:560 [inline] [<ffffffff82712f0d>] really_probe+0x12d/0x390 drivers/base/dd.c:639 [<ffffffff8271322f>] __driver_probe_device+0xbf/0x140 drivers/base/dd.c:778 Fix this bug by rewriting the error handling code in ufx_usb_probe.

Affected

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

v ≥ 4.14.298v ≥ 4.19.264v ≥ 4.9.332v ≥ 6.0.7v < 5.4.2324.14.298 ≤ v < 4.154.19.264 ≤ v < 4.204.9.332 ≤ v < 4.105.10.153 ≤ v < 5.10.1685.11 ≤ v < 5.15.935.15.77 ≤ v < 5.15.935.16 ≤ v < 6.1.115.4.223 ≤ v < 5.4.2325.5 ≤ v < 5.10.1686.0.7 ≤ v < 6.16.1 ≤ v < 6.1.116.1 ≤ v < 6.23f40852d671072836fb7ae331a1f28a24223c4e84.14.2984.19.2644.9.3325.10.1535.15.775.4.2235385af2f89bc352fb70753ab41b2bb036190141f6.0.76.16f2075ea883e5d7730d0c9ebb1bb8e7a1a7e953f70faf9d9b6cc74418716bbf76fe75bd2da10ad4a8d924b262f3178a9b17c17d4306a9f426c508bd9cc67482c9e5f2c80d62f623bcc347c29f9f648e1cc6a7249842fceda7574ceb63275a2d5e99d2862d9ddfeb01fb95ffbbc7031d46a5ee2a5e45cbb86
Vendor states this is fixed in 1b4c08844628dfc8d72d3f51b657f2a5e63b7b4b (fixed)
Vendor states this is fixed in 3931014367ef31d26af65386a4ca496f50f0cfdf (fixed)
Vendor states this is fixed in 3b3d3127f5b4291ae4caaf50f7b66089ad600480 (fixed)
Vendor states this is fixed in 64fa364ad3245508d393e16ed4886f92d7eb423c (fixed)
Vendor states this is fixed in b76449ee75e21acfe9fa4c653d8598f191ed7d68 (fixed)
Affected range stops below 4.10, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.20, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.10.168 (unaffected)
Vendor states this is fixed in 5.15.93 (unaffected)
Vendor states this is fixed in 5.4.232 (unaffected)
Vendor states this is fixed in 6.1 (unaffected)
Vendor states this is fixed in 6.1.11 (unaffected)
Vendor states this is fixed in 6.2 (unaffected)

References (5)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/1b4c08844628dfc8d72d3f51b657f2a5e63b7b4b
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/3931014367ef31d26af65386a4ca496f50f0cfdf
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/3b3d3127f5b4291ae4caaf50f7b66089ad600480
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/64fa364ad3245508d393e16ed4886f92d7eb423c
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/b76449ee75e21acfe9fa4c653d8598f191ed7d68

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

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

Quick Info

StatusMODIFIED
CWE
CWE-401

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