Kernel warning via disabled USB endpoint queue
Published May 17, 2024 · Updated May 11, 2026
Race condition in Linux kernel USB gadget UDC code allows local users to trigger a kernel warning during mass-storage teardown. The mass-storage function's main thread can call usb_ep_queue() after another thread disables the endpoint, causing WARN_ON_ONCE() to emit a warning. The USB mass-storage gadget must be active during concurrent function disable; the kernel record reports no driver failure beyond the diagnostic.
Summary
What happened
Race condition in Linux kernel USB gadget UDC code allows local users to trigger a kernel warning during mass-storage teardown. The mass-storage function's main thread can call usb_ep_queue() after another thread disables the endpoint, causing WARN_ON_ONCE() to emit a warning. The USB mass-storage gadget must be active during concurrent function disable; the kernel record reports no driver failure beyond the diagnostic.
The record
- CVE
- CVE-2024-35822
- Published
- May 17, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 17, 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=4.5
- Affected versionversion=8a0859b65b06ea07461271ce4f1fe25b48d1ec55 <2a587a035214fa1b5ef598aea0b81848c5b72e5e
- Affected versionversion=8a0859b65b06ea07461271ce4f1fe25b48d1ec55 <2b002c308e184feeaeb72987bca3f1b11e5f70b8
- Affected versionversion=8a0859b65b06ea07461271ce4f1fe25b48d1ec55 <30511676eb54d480d014352bf784f02577a10252
- Affected versionversion=8a0859b65b06ea07461271ce4f1fe25b48d1ec55 <36177c2595df12225b95ce74eb1ac77b43d5a58c
- Affected versionversion=8a0859b65b06ea07461271ce4f1fe25b48d1ec55 <3e944ddc17c042945d983e006df7860687a8849a
- Affected versionversion=8a0859b65b06ea07461271ce4f1fe25b48d1ec55 <68d951880d0c52c7f13dcefb5501b69b8605ce8c
- Affected versionversion=8a0859b65b06ea07461271ce4f1fe25b48d1ec55 <99731076722eb7ed26b0c87c879da7bb71d24290
- Affected versionversion=8a0859b65b06ea07461271ce4f1fe25b48d1ec55 <df5cbb908f1687e8ab97e222a16b7890d5501acf
- Affected versionversion=8a0859b65b06ea07461271ce4f1fe25b48d1ec55 <f74c5e0b54b02706d9a862ac6cddade30ac86bcf
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
No sourced classifications are available.
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