CVE-2022-50028

gadgetfs: ep_io - wait until IRQ finishes

MEDIUM

5.5

CVSS Score

Published: June 18, 2025 at 11:01 AM UTC

Updated: August 5, 2026 at 09:24 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

v < 4.9.3262.6.12 ≤ v < 4.14.2912.6.12 ≤ v < 4.19.2562.6.12 ≤ v < 4.9.3262.6.12 ≤ v < 5.10.1382.6.12 ≤ v < 5.15.632.6.12 ≤ v < 5.19.42.6.12 ≤ v < 5.4.2112.6.12 ≤ v < 6.04.10 ≤ v < 4.14.2914.15 ≤ v < 4.19.2564.20 ≤ v < 5.4.2115.11 ≤ v < 5.15.635.16 ≤ v < 5.19.45.5 ≤ v < 5.10.1381da177e4c3f41524e886b7f1b8a0c1fc7321cac2 2.6.12

Vendor states this is fixed in 04cb742d4d8f30dc2e83b46ac317eec09191c68e (fixed)

Vendor states this is fixed in 118d967ce00a3d128bf731b35e4e2cb0facf5f00 (fixed)

Vendor states this is fixed in 2b06d5d97c0e067108a122986767731d40742138 (fixed)

Vendor states this is fixed in 67a4874461422e633236a0286a01b483cd647113 (fixed)

Vendor states this is fixed in 77040efe59a141286d090c8a0d37c65a355a1832 (fixed)

Vendor states this is fixed in 94aadba8d000d5de56af4ce8da3f334f21bf7a79 (fixed)

Vendor states this is fixed in 9ac14f973cb91f0c01776517e6d50981f32b8038 (fixed)

Vendor states this is fixed in ca06b4cde54f8ec8be3aa53fd339bd56e62c12b3 (fixed)

Vendor states this is fixed in 2.6.12 (unaffected)

Vendor states this is fixed in 4.14.291 (unaffected)

Vendor states this is fixed in 4.19.256 (unaffected)

Vendor states this is fixed in 4.9.326 (unaffected)