https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 06:23:29 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-14137 bdu:2025-14137 https://cve.radiocsirt.org/vuln/bdu:2025-14137 https://cve.radiocsirt.org/vuln/bell-cve-2024-50100 <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2024-50100 https://cve.radiocsirt.org/vuln/certfr-2024-avi-1102 certfr-2024-avi-1102 https://cve.radiocsirt.org/vuln/certfr-2024-avi-1102 https://cve.radiocsirt.org/vuln/euvd-2026-313485 EUVD-2026-313485 https://cve.radiocsirt.org/vuln/euvd-2026-313485 https://cve.radiocsirt.org/vuln/fkie_cve-2024-50100 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>USB: gadget: dummy-hcd: Fix &#34;task hung&#34; problem</p> <p>The syzbot fuzzer has been encountering &#34;task hung&#34; 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.</p> <p>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.</p> <p>Since hrtimers have no API for telling when they are queued and the callback isn&#39;t running, the driver must keep track of this for itself. That&#39;s what this patch does, adding a new &#34;timer_pending&#34; flag and setting or clearing it at the appropriate times.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>USB: gadget: dummy-hcd: Fix &#34;task hung&#34; problem</p> <p>The syzbot fuzzer has been encountering &#34;task hung&#34; 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.</p> <p>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.</p> <p>Since hrtimers have no API for telling when they are queued and the callback isn&#39;t running, the driver must keep track of this for itself. That&#39;s what this patch does, adding a new &#34;timer_pending&#34; flag and setting or clearing it at the appropriate times.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-50100 https://cve.radiocsirt.org/vuln/ghsa-66q2-ffpq-62mp <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>USB: gadget: dummy-hcd: Fix &#34;task hung&#34; problem</p> <p>The syzbot fuzzer has been encountering &#34;task hung&#34; 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.</p> <p>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.</p> <p>Since hrtimers have no API for telling when they are queued and the callback isn&#39;t running, the driver must keep track of this for itself. That&#39;s what this patch does, adding a new &#34;timer_pending&#34; flag and setting or clearing it at the appropriate times.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>USB: gadget: dummy-hcd: Fix &#34;task hung&#34; problem</p> <p>The syzbot fuzzer has been encountering &#34;task hung&#34; 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.</p> <p>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.</p> <p>Since hrtimers have no API for telling when they are queued and the callback isn&#39;t running, the driver must keep track of this for itself. That&#39;s what this patch does, adding a new &#34;timer_pending&#34; flag and setting or clearing it at the appropriate times.</p> https://cve.radiocsirt.org/vuln/ghsa-66q2-ffpq-62mp https://cve.radiocsirt.org/vuln/opensuse-su-2024:14500-1 <p>kernel-devel-6.11.8-1.1 on GA media</p> <p>kernel-devel-6.11.8-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2024:14500-1 https://cve.radiocsirt.org/vuln/suse-su-2024:4314-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2024:4314-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-50100 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 67 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: USB: gadget: dummy-hcd: Fix &#34;task hung&#34; problem The syzbot fuzzer has been encountering &#34;task hung&#34; 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&#39;t running, the driver must keep track of this for itself. That&#39;s what this patch does, adding a new &#34;timer_pending&#34; flag and setting or clearing it at the appropriate times.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 67 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: USB: gadget: dummy-hcd: Fix &#34;task hung&#34; problem The syzbot fuzzer has been encountering &#34;task hung&#34; 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&#39;t running, the driver must keep track of this for itself. That&#39;s what this patch does, adding a new &#34;timer_pending&#34; flag and setting or clearing it at the appropriate times.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-50100 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3339 <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.</p> <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3339