CVE-2022-50028: gadgetfs: ep_io - wait until IRQ finishes
In the Linux kernel, the following vulnerability has been resolved:
gadgetfs: ep_io - wait until IRQ finishes
after usb_ep_queue() if wait_for_completion_interruptible() is
interrupted we need to wait until IRQ gets finished.
Otherwise complete() from epio_complete() can corrupt stack.
Security readout for executives and security teams
Plain-English summary
A timing flaw in Linux USB gadgetfs can leave an interrupt handler using stack data after the waiting operation has ended, corrupting kernel memory. Successful abuse could affect confidentiality, integrity, and availability. The supplied CVSS indicates that an attacker needs low-privileged local access; this is not described as a remote, internet-facing vulnerability.
Executive priority
Treat this as an accelerated, exposure-based patching item. Prioritize multi-user systems, embedded devices, and USB gadget hosts where untrusted local users can reach gadgetfs. It does not warrant internet-wide emergency response based solely on the supplied evidence, but kernel memory corruption justifies prompt remediation where prerequisites exist.
Technical view
If gadgetfs ep_io is interrupted after usb_ep_queue(), it can return before the USB request's IRQ completion finishes. epio_complete() may then call complete() against expired stack state, causing stack corruption. The upstream resolution waits for IRQ completion before allowing that state to leave scope.
Likely exposure
Exposure is most likely on systems running an affected Linux kernel where gadgetfs endpoint I/O is enabled and reachable by low-privileged local users. The record names several versions from 2.6.12 through 6.0, but its formatting is insufficient to infer exact continuous affected ranges or distribution package versions.
Exploitation context
The CVSS vector describes local access, low complexity, low privileges, and no user interaction. The supplied record is not in CISA KEV and provides no evidence of active exploitation or a public proof of concept. Absence from these sources does not prove exploitation is impossible.
Researcher notes
This is an asynchronous lifetime race involving interruption of a completion wait and later IRQ completion against stack-backed state. The linked stable commits are the strongest remediation evidence supplied. Exact exploitability, affected configuration requirements, distribution backports, and real-world attack prevalence are not established by the bundle.
Mitigation direction
Apply the applicable upstream stable fix or a vendor kernel package containing its backport.
Consult the Linux distribution or device vendor for exact fixed package versions.
Until updated, limit untrusted local access to systems exposing gadgetfs where operationally feasible.
After updating, boot the fixed kernel and confirm it is the active version.
Validation and detection
Inventory running kernel builds on systems that support USB gadget functionality.
Determine whether gadgetfs is configured and accessible to low-privileged local users.
Map each kernel build to an applicable linked stable commit or documented vendor backport.
After remediation, verify the active kernel contains the fix and test USB gadget workflows.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2022-50028 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
9Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.