Kernel memory corruption via interrupted gadgetfs I/O
Published Jun 18, 2025 · Updated Aug 5, 2026
Stack corruption in Linux kernel gadgetfs allows local users to corrupt kernel memory via interrupted synchronous endpoint I/O. After usb_ep_queue(), ep_io returns when wait_for_completion_interruptible() is interrupted without waiting for the IRQ callback, leaving epio_complete() to call complete() on an expired stack completion object. An unprivileged user with access to an active gadgetfs endpoint can control the signal-and-teardown sequence, enabling kernel memory disclosure, modification, or a panic.
Summary
What happened
Stack corruption in Linux kernel gadgetfs allows local users to corrupt kernel memory via interrupted synchronous endpoint I/O. After usb_ep_queue(), ep_io returns when wait_for_completion_interruptible() is interrupted without waiting for the IRQ callback, leaving epio_complete() to call complete() on an expired stack completion object. An unprivileged user with access to an active gadgetfs endpoint can control the signal-and-teardown sequence, enabling kernel memory disclosure, modification, or a panic.
The record
- CVE
- CVE-2022-50028
- Published
- Jun 18, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 18, 2025CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <04cb742d4d8f30dc2e83b46ac317eec09191c68e
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <118d967ce00a3d128bf731b35e4e2cb0facf5f00
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2b06d5d97c0e067108a122986767731d40742138
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <67a4874461422e633236a0286a01b483cd647113
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <77040efe59a141286d090c8a0d37c65a355a1832
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <94aadba8d000d5de56af4ce8da3f334f21bf7a79
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9ac14f973cb91f0c01776517e6d50981f32b8038
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ca06b4cde54f8ec8be3aa53fd339bd56e62c12b3
- Affected versionversion=2.6.12
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