Kernel-memory exhaustion via mismatched probe cleanup
Published Mar 27, 2025 · Updated May 23, 2026
Memory leak in the Linux kernel smscufx framebuffer driver allows local users to exhaust kernel memory through USB device probing. The ufx_usb_probe error paths apply mismatched cleanup: some omit ufx_free_usb_list, while others release resources under the wrong labels. Exploitation requires local low-privileged access and repeated failing probes of a supported USB display device, causing availability loss as unreleased allocations consume kernel memory.
Summary
What happened
Memory leak in the Linux kernel smscufx framebuffer driver allows local users to exhaust kernel memory through USB device probing. The ufx_usb_probe error paths apply mismatched cleanup: some omit ufx_free_usb_list, while others release resources under the wrong labels. Exploitation requires local low-privileged access and repeated failing probes of a supported USB display device, causing availability loss as unreleased allocations consume kernel memory.
The record
- CVE
- CVE-2022-49741
- Published
- Mar 27, 2025
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 27, 2025CVE publishedPublication date reported by the CVE source.
- May 23, 2026Record 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=3f40852d671072836fb7ae331a1f28a24223c4e8
- Affected versionversion=4.14.298 <4.15
- Affected versionversion=4.19.264 <4.20
- Affected versionversion=4.9.332 <4.10
- Affected versionversion=5.10.153 <5.10.168
- Affected versionversion=5.15.77 <5.15.93
- Affected versionversion=5385af2f89bc352fb70753ab41b2bb036190141f <3b3d3127f5b4291ae4caaf50f7b66089ad600480
- Affected versionversion=5.4.223 <5.4.232
- Affected versionversion=6.0.7 <6.1
- Affected versionversion=6.1
- Affected versionversion=6f2075ea883e5d7730d0c9ebb1bb8e7a1a7e953f
- Affected versionversion=70faf9d9b6cc74418716bbf76fe75bd2da10ad4a
- Affected versionversion=8d924b262f3178a9b17c17d4306a9f426c508bd9
- Affected versionversion=cc67482c9e5f2c80d62f623bcc347c29f9f648e1 <1b4c08844628dfc8d72d3f51b657f2a5e63b7b4b
- Affected versionversion=cc67482c9e5f2c80d62f623bcc347c29f9f648e1 <b76449ee75e21acfe9fa4c653d8598f191ed7d68
- Affected versionversion=cc6a7249842fceda7574ceb63275a2d5e99d2862 <64fa364ad3245508d393e16ed4886f92d7eb423c
- Affected versionversion=d9ddfeb01fb95ffbbc7031d46a5ee2a5e45cbb86 <3931014367ef31d26af65386a4ca496f50f0cfdf
What conditions does exploitation require?
What is affected?
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
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