Kernel memory corruption via oversized UVC transfer
Published Oct 21, 2024 · Updated May 11, 2026
Buffer overflow in affected Linux kernel versions allows local users to overwrite four bytes via a crafted UVC OUT control transfer. The uvc_function_setup data-stage handler copies req->actual bytes into the 60-byte uvc_event->data.data array even though setup accepts payloads up to 64 bytes. Reachability requires the USB gadget UVC function and the ability to submit an OUT control request; the documented result is a four-byte kernel-memory overwrite.
Summary
What happened
Buffer overflow in affected Linux kernel versions allows local users to overwrite four bytes via a crafted UVC OUT control transfer. The uvc_function_setup data-stage handler copies req->actual bytes into the 60-byte uvc_event->data.data array even though setup accepts payloads up to 64 bytes. Reachability requires the USB gadget UVC function and the ability to submit an OUT control request; the documented result is a four-byte kernel-memory overwrite.
The record
- CVE
- CVE-2022-48948
- Published
- Oct 21, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-120
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 21, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 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=2.6.35
- Affected versionversion=cdda479f15cd13fa50a913ca85129c0437cc7b91 <06fd17ee92c8f1704c7e54ec0fd50ae0542a49a5
- Affected versionversion=cdda479f15cd13fa50a913ca85129c0437cc7b91 <4972e3528b968665b596b5434764ff8fd9446d35
- Affected versionversion=cdda479f15cd13fa50a913ca85129c0437cc7b91 <4c92670b16727365699fe4b19ed32013bab2c107
- Affected versionversion=cdda479f15cd13fa50a913ca85129c0437cc7b91 <6b41a35b41f77821db24f2d8f66794b390a585c5
- Affected versionversion=cdda479f15cd13fa50a913ca85129c0437cc7b91 <7b1f773277a72f9756d47a41b94e43506cce1954
- Affected versionversion=cdda479f15cd13fa50a913ca85129c0437cc7b91 <b8fb1cba934ea122b50f13a4f9d6fc4fdc43d2be
- Affected versionversion=cdda479f15cd13fa50a913ca85129c0437cc7b91 <bc8380fe5768c564f921f7b4eaba932e330b9e4b
- Affected versionversion=cdda479f15cd13fa50a913ca85129c0437cc7b91 <c79538f32df12887f110dcd6b9c825b482905f24
- Affected versionversion=cdda479f15cd13fa50a913ca85129c0437cc7b91 <d1a92bb8d697f170d93fe922da763d7d156b8841
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
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