CVE-2022-50767
Description
In the Linux kernel, the following vulnerability has been resolved:
fbdev: smscufx: Fix several use-after-free bugs
Several types of UAFs can occur when physically removing a USB device.
Adds ufx_ops_destroy() function to .fb_destroy of fb_ops, and in this function, there is kref_put() that finally calls ufx_free().
This fix prevents multiple UAFs.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Multiple use-after-free bugs in the Linux kernel's smscufx framebuffer driver can be triggered by physically removing a USB device.
Vulnerability
Description
CVE-2022-50767 describes several use-after-free (UAF) vulnerabilities in the Linux kernel's smscufx framebuffer driver. The root cause is improper handling of device removal: when a USB device is physically disconnected, the driver's data structures can be freed while still being accessed, leading to UAF conditions [1][2][3].
Exploitation
An attacker with physical access to a system using the affected driver can trigger these UAFs by simply unplugging the USB device. No authentication or special privileges are required beyond the ability to physically remove the device. The attack surface is limited to systems with the smscufx driver loaded and a compatible USB display adapter attached [1][2][3].
Impact
Successful exploitation could allow an attacker to cause a denial-of-service the system (kernel crash) or potentially execute arbitrary code in kernel context, depending on the specific UAF scenario. The vulnerabilities are classified as high severity due to the possibility of privilege escalation privilege escalation [1][2][3].
Mitigation
The fix introduces a ufx_ops_destroy() function assigned to fb_ops.fb_destroy, which uses kref_put() to safely release the device only after all references are dropped. This prevents the UAFs by ensuring proper reference counting during device removal. The patch has been applied to the Linux kernel stable branches [1][2][3]. Users should update to a kernel version containing the fix.
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2Patches
86f2075ea883e3f40852d671070faf9d9b6cc5385af2f89bcd9ddfeb01fb9cc6a7249842f8d924b262f31cc67482c9e5fVulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
8- git.kernel.org/stable/c/3f40852d671072836fb7ae331a1f28a24223c4e8nvd
- git.kernel.org/stable/c/5385af2f89bc352fb70753ab41b2bb036190141fnvd
- git.kernel.org/stable/c/6f2075ea883e5d7730d0c9ebb1bb8e7a1a7e953fnvd
- git.kernel.org/stable/c/70faf9d9b6cc74418716bbf76fe75bd2da10ad4anvd
- git.kernel.org/stable/c/8d924b262f3178a9b17c17d4306a9f426c508bd9nvd
- git.kernel.org/stable/c/cc67482c9e5f2c80d62f623bcc347c29f9f648e1nvd
- git.kernel.org/stable/c/cc6a7249842fceda7574ceb63275a2d5e99d2862nvd
- git.kernel.org/stable/c/d9ddfeb01fb95ffbbc7031d46a5ee2a5e45cbb86nvd
News mentions
0No linked articles in our index yet.