CVE-2024-50100
Last modified
CVE-2024-50100 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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. EPSS estimates a 0.23% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.10, < 6.11.5 | — |
| Linux | Linux Kernel | 6.12 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2024-50100?
How severe is CVE-2024-50100?
How do I fix CVE-2024-50100?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2024
- CVE-2024-50095In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-50096In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-50097In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-50098In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-50099In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-5010In WhatsUp Gold versions released before 2023.1.3, a vulnera…7.5
- CVE-2024-50101In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-50102In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-50103In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-50104In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-50105In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-50106In the Linux kernel, the following vulnerability has been re…7
Are you affected by CVE-2024-50100?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
