LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49741: fbdev: smscufx: fix error handling code in ufx_usb_probe

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.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-49741 is a Linux kernel memory leak in the smscufx framebuffer USB driver’s device-probe error handling. The known impact is availability: repeated triggering could consume kernel memory and degrade or crash a system. The source bundle does not show data theft, privilege escalation, or active exploitation.

Executive priority

Treat this as a moderate availability risk. It is not currently evidenced as internet-exploited, but kernel memory leaks can affect reliability on shared or locally accessible systems. Patch through normal kernel maintenance, with higher priority where untrusted local users or peripheral access are in scope.

Technical view

The bug is CWE-401 in drivers/video/fbdev/smscufx.c, specifically ufx_usb_probe error paths with mismatched cleanup such as missing ufx_free_usb_list and incorrect cmap/framebuffer cleanup. Syzkaller reported an unreferenced allocation from ufx_alloc_urb_list. CVSS 3.1 is 5.5: local, low privilege, no user interaction, high availability impact.

Likely exposure

Exposure is most relevant to Linux systems running affected kernel versions with the smscufx framebuffer USB driver present and reachable. The bundle lists Linux versions including 5.4.232, 5.10.168, 5.15.93, 6.1, 6.1.11, and 6.2 as affected. Systems without this driver or with fixed stable commits are less likely exposed.

Exploitation context

The source bundle does not cite CISA KEV listing or active exploitation. Evidence comes from local syzkaller testing that found a memory leak during USB probe error handling. Based on the CVSS vector, exploitation would require local access with low privileges and targets availability rather than confidentiality or integrity.

Researcher notes

The key evidence is the kernel fix description and syzkaller leak trace. The affected-data bundle mixes kernel release numbers and commit identifiers, so validation should rely on vendor backport status, not version strings alone. No exploit, proof-of-concept, or non-availability impact is provided.

Mitigation direction

  • Update affected Linux kernels to builds containing the referenced stable fixes.
  • Check your Linux distribution advisory for backported fixes and package names.
  • Prioritize systems allowing local users or peripheral interaction with this driver path.
  • If patching is delayed, follow vendor guidance for reducing driver exposure.
  • Track kernel versions against the affected list and fixed stable commits.

Validation and detection

  • Inventory Linux kernel versions across servers, workstations, and appliances.
  • Check whether smscufx support is built, installed, or loadable on exposed systems.
  • Confirm vendor kernel packages include one of the referenced stable fixes.
  • Review vulnerability scanner findings against actual kernel package backport status.
  • Monitor for unexplained kernel memory pressure on potentially affected systems.
Prepared
Confidence
high
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-401: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-49741 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2022-49741Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux5385af2f89bc352fb70753ab41b2bb036190141f, d9ddfeb01fb95ffbbc7031d46a5ee2a5e45cbb86, cc6a7249842fceda7574ceb63275a2d5e99d2862, cc67482c9e5f2c80d62f623bcc347c29f9f648e1, cc67482c9e5f2c80d62f623bcc347c29f9f648e1, 6f2075ea883e5d7730d0c9ebb1bb8e7a1a7e953f, 3f40852d671072836fb7ae331a1f28a24223c4e8, 70faf9d9b6cc74418716bbf76fe75bd2da10ad4a, 8d924b262f3178a9b17c17d4306a9f426c508bd9unaffected
LinuxLinux6.1, 0, 5.4.232, 5.10.168, 5.15.93, 6.1.11, 6.2affected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-401 · source CWE mapping

Missing Release of Memory after Effective Lifetime

Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.