5.5

CVE-2024-50100: USB: gadget: dummy-hcd: Fix "task hung" problem

Modified
AliasesUBUNTU-CVE-2024-50100DEBIAN-CVE-2024-50100
Published 05-11-2024Last modified 11-05-2026

Vulnerability summary

CVE-2024-50100 is a medium (CVSS 5.5) vulnerability in linux. EPSS estimates a 0.24% chance of exploitation in the next 30 days, higher than 14.5% of scored vulnerabilities.

Priority
Routine

Not severe (CVSS 5.5, local access); no exploitation reported by the 5 checked sources

Source freshness unavailable

How is this decided?
CVSS score
5.5/10
010
Medium · v3.1 (CVE.org)
EPSS score
0.24%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 11 · Related 13

Timeline

  1. 05-11-2024
    PublishedVulnerability first disclosed.
  2. 11-05-2026
    Last modifiedVulnerability information updated.

Description

In the Linux kernel, the following vulnerability has been resolved: USB: gadget: dummy-hcd: Fix "task hung" problem The syzbot fuzzer has been encountering "task hung" problems ever since the dummy-hcd driver was changed to use hrtimers instead of regular timers. It turns out that the problems are caused by a subtle difference between the timer_pending() and hrtimer_active() APIs. The changeover blindly replaced the first by the second. However, timer_pending() returns True when the timer is queued but not when its callback is running, whereas hrtimer_active() returns True when the hrtimer is queued _or_ its callback is running. This difference occasionally caused dummy_urb_enqueue() to think that the callback routine had not yet started when in fact it was almost finished. As a result the hrtimer was not restarted, which made it impossible for the driver to dequeue later the URB that was just enqueued. This caused usb_kill_urb() to hang, and things got worse from there. Since hrtimers have no API for telling when they are queued and the callback isn't running, the driver must keep track of this for itself. That's what this patch does, adding a new "timer_pending" flag and setting or clearing it at the appropriate times.

CVSS metrics

4 scores · 4 sources · 1 version

EPSS trend

Probability

0.24%

Chance of exploitation in the next 30 days

Percentile

15%

Versus all other CVEs

30-day change

No change 0.00 pp

From 0.24% on 04-10-2026

04-10-202603-11-2026

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

No weakness data has been published for this record.

Affected systems

Version check

Known conditions: local access, low-privilege account, no user interaction (CVSS vector). Other conditions: not stated in public data.

Ubuntu76 products
  • linux-allwinner-5.19All versions (No fix recorded)
  • linux-aws-5.0All versions (No fix recorded)
  • linux-aws-5.11All versions (No fix recorded)
  • linux-aws-5.13All versions (No fix recorded)
  • linux-aws-5.19All versions (No fix recorded)
Linux2 products
  • linux≥ 8ffba8d917f44a8acbfccbdec331204353ac8ac8, < cf7ee2291da551fc4b109fda1f6a332cb8212065 | ≥ 4a4cb56556124027f4846ff30849c0ede981aa92, < 7d85884576a3be3616c260fc1fa862a59579d1ab | ≥ a7f3813e589fd8e2834720829a47b5eb914a9afe, < f828205ee3e4ddc712a13fba6c9902d51e91ddaf | ≥ a7f3813e589fd8e2834720829a47b5eb914a9afe, < 5189df7b8088268012882c220d6aca4e64981348 | 6.10
  • linux_kernel≥ 6.10, < 6.11.5 | 6.12:rc1 | 6.12:rc2 | 6.12:rc3
Debian1 product
  • linux< 6.11.5-1

3 vendors · 79 products

References

11 links
Show all 11 references