fbdev: smscufx: fix error handling code in ufx_usb_probe

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.

Scores

EPSS (exploitation in 30 days)

0.19% · top 91% of all CVEs (7 Nov 2026)

CISA SSVC

Exploitation: none · Automatable: no · Technical impact: partial

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Weakness

• CWE-401 Missing Release of Memory after Effective Lifetime (opens in a new tab)All about CWE-401 and its CVEs

Affected products

• Linux · Linux

  • affected 5385af2f89bc352fb70753ab41b2bb036190141f – < 3b3d3127f5b4291ae4caaf50f7b66089ad600480
  • affected d9ddfeb01fb95ffbbc7031d46a5ee2a5e45cbb86 – < 3931014367ef31d26af65386a4ca496f50f0cfdf
  • affected cc6a7249842fceda7574ceb63275a2d5e99d2862 – < 64fa364ad3245508d393e16ed4886f92d7eb423c
  • affected cc67482c9e5f2c80d62f623bcc347c29f9f648e1 – < 1b4c08844628dfc8d72d3f51b657f2a5e63b7b4b
  • affected cc67482c9e5f2c80d62f623bcc347c29f9f648e1 – < b76449ee75e21acfe9fa4c653d8598f191ed7d68
  • affected 6f2075ea883e5d7730d0c9ebb1bb8e7a1a7e953f
  • affected 3f40852d671072836fb7ae331a1f28a24223c4e8
  • affected 70faf9d9b6cc74418716bbf76fe75bd2da10ad4a
  • affected 8d924b262f3178a9b17c17d4306a9f426c508bd9
  • affected 5.4.223 – < 5.4.232
  • affected 5.10.153 – < 5.10.168
  • affected 5.15.77 – < 5.15.93
  • affected 4.9.332 – < 4.10
  • affected 4.14.298 – < 4.15
  • affected 4.19.264 – < 4.20
  • affected 6.0.7 – < 6.1

• Linux · Linux

  • affected 6.1
  • unaffected < 6.1
  • unaffected 5.4.232 – ≤ 5.4.*
  • unaffected 5.10.168 – ≤ 5.10.*
  • unaffected 5.15.93 – ≤ 5.15.*
  • unaffected 6.1.11 – ≤ 6.1.*
  • unaffected 6.2 – ≤ *

References (5)

• https://git.kernel.org/stable/c/3b3d3127f5b4291ae4caaf50f7b66089ad600480 (opens in a new tab)
• https://git.kernel.org/stable/c/3931014367ef31d26af65386a4ca496f50f0cfdf (opens in a new tab)
• https://git.kernel.org/stable/c/64fa364ad3245508d393e16ed4886f92d7eb423c (opens in a new tab)
• https://git.kernel.org/stable/c/1b4c08844628dfc8d72d3f51b657f2a5e63b7b4b (opens in a new tab)
• https://git.kernel.org/stable/c/b76449ee75e21acfe9fa4c653d8598f191ed7d68 (opens in a new tab)

Sources

The same CVE in the primary databases and aggregators, to check against.

• CVE.org record (opens in a new tab)
• CVE List JSON (GitHub) (opens in a new tab)
• NVD (opens in a new tab)
• FIRST EPSS (opens in a new tab)
• OSV.dev (opens in a new tab)
• GitHub Advisories (opens in a new tab)
• CIRCL Vulnerability-Lookup (opens in a new tab)

Badge for a README or a ticket

[![CVE-2022-49741](https://trackcve.app/badge/CVE-2022-49741.svg)](https://trackcve.app/cve/CVE-2022-49741)

Record last updated 23 May 2026, 15:22 UTC.