Kernel memory corruption via physical USB removal
Published Dec 24, 2025 · Updated Dec 24, 2025
Use-after-free in Linux smscufx before 6.1 allows physically proximate attackers to corrupt kernel memory by removing a USB device. The driver's framebuffer teardown lacks a .fb_destroy callback that releases the final ufx reference, so USB-managed state can be freed while framebuffer users still retain it. Exploitation requires physical access to remove an attached device using the smscufx driver; the public record does not establish code execution or data disclosure.
Summary
What happened
Use-after-free in Linux smscufx before 6.1 allows physically proximate attackers to corrupt kernel memory by removing a USB device. The driver's framebuffer teardown lacks a .fb_destroy callback that releases the final ufx reference, so USB-managed state can be freed while framebuffer users still retain it. Exploitation requires physical access to remove an attached device using the smscufx driver; the public record does not establish code execution or data disclosure.
The record
- CVE
- CVE-2022-50767
- Published
- Dec 24, 2025
- Updated
- Dec 24, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- physical
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 24, 2025CVE publishedPublication date reported by the CVE source.
- Dec 24, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3f40852d671072836fb7ae331a1f28a24223c4e8
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5385af2f89bc352fb70753ab41b2bb036190141f
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6f2075ea883e5d7730d0c9ebb1bb8e7a1a7e953f
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <70faf9d9b6cc74418716bbf76fe75bd2da10ad4a
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8d924b262f3178a9b17c17d4306a9f426c508bd9
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <cc67482c9e5f2c80d62f623bcc347c29f9f648e1
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <cc6a7249842fceda7574ceb63275a2d5e99d2862
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d9ddfeb01fb95ffbbc7031d46a5ee2a5e45cbb86
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo