CVE-2024-35822: usb: udc: remove warning when queue disabled ep
In the Linux kernel, the following vulnerability has been resolved:
usb: udc: remove warning when queue disabled ep
It is possible trigger below warning message from mass storage function,
WARNING: CPU: 6 PID: 3839 at drivers/usb/gadget/udc/core.c:294 usb_ep_queue+0x7c/0x104
pc : usb_ep_queue+0x7c/0x104
lr : fsg_main_thread+0x494/0x1b3c
Root cause is mass storage function try to queue request from main thread,
but other thread may already disable ep when function disable.
As there is no function failure in the driver, in order to avoid effort
to fix warning, change WARN_ON_ONCE() in usb_ep_queue() to pr_debug().
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue concerns a USB gadget mass-storage code path that can trigger a kernel warning when an endpoint is disabled by another thread. The source says there is no driver function failure, and the fix lowers the warning to debug logging. Business urgency appears low unless your products rely on Linux USB gadget functionality.
Executive priority
Treat as low priority for general server fleets, but include it in normal kernel patch cycles. Raise priority for embedded products, appliances, or lab systems that expose Linux USB gadget mass-storage behavior.
Technical view
CVE-2024-35822 is in the Linux USB gadget UDC core. The mass-storage function may queue a request while another thread has disabled the endpoint, causing a WARN_ON_ONCE in usb_ep_queue. Upstream stable commits resolve it by changing that warning to pr_debug, based on the stated absence of driver failure.
Likely exposure
Exposure is most plausible on Linux systems using USB gadget/UDC mass-storage functionality, often embedded or device-style deployments. The bundle lists Linux as affected across several kernel version lines, but does not provide CPEs, CVSS, or a complete product matrix.
Exploitation context
The bundle does not cite active exploitation, public exploit use, or CISA KEV listing. The described impact is a warning condition, not confirmed code execution, privilege escalation, data loss, or service failure.
Researcher notes
Evidence is narrow: the CVE text states the warning can be triggered but also says no driver failure occurs. No CWE, CVSS, CPEs, or exploitation evidence are provided. Avoid broad impact claims without vendor-specific advisories.
Mitigation direction
Apply vendor or distribution kernel updates containing the referenced stable commits.
Prioritize systems that use Linux USB gadget or mass-storage device functionality.
For Debian LTS systems, review the cited Debian LTS advisories.
If updates are unavailable, follow your kernel vendor guidance.
Track future CVE updates because severity and CVSS are absent here.
Validation and detection
Inventory Linux kernel versions on systems with USB gadget functionality.
Check whether the running kernel includes the referenced upstream stable fix.
Review distro security advisories for package-level backports.
Look for historical usb_ep_queue WARN_ON messages in kernel logs.
Confirm whether USB mass-storage gadget code is enabled or used.
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-2024-35822 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.