https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 20:39:24 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-02656 bdu:2026-02656 https://cve.radiocsirt.org/vuln/bdu:2026-02656 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0587 certfr-2025-avi-0587 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0587 https://cve.radiocsirt.org/vuln/euvd-2026-310925 EUVD-2026-310925 https://cve.radiocsirt.org/vuln/euvd-2026-310925 https://cve.radiocsirt.org/vuln/fkie_cve-2022-49954 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>Input: iforce - wake up after clearing IFORCE_XMIT_RUNNING flag</p> <p>syzbot is reporting hung task at __input_unregister_device() [1], for iforce_close() waiting at wait_event_interruptible() with dev-&gt;mutex held is blocking input_disconnect_device() from __input_unregister_device().</p> <p>It seems that the cause is simply that commit c2b27ef672992a20 (&#34;Input: iforce - wait for command completion when closing the device&#34;) forgot to call wake_up() after clear_bit().</p> <p>Fix this problem by introducing a helper that calls clear_bit() followed by wake_up_all().</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>Input: iforce - wake up after clearing IFORCE_XMIT_RUNNING flag</p> <p>syzbot is reporting hung task at __input_unregister_device() [1], for iforce_close() waiting at wait_event_interruptible() with dev-&gt;mutex held is blocking input_disconnect_device() from __input_unregister_device().</p> <p>It seems that the cause is simply that commit c2b27ef672992a20 (&#34;Input: iforce - wait for command completion when closing the device&#34;) forgot to call wake_up() after clear_bit().</p> <p>Fix this problem by introducing a helper that calls clear_bit() followed by wake_up_all().</p> https://cve.radiocsirt.org/vuln/fkie_cve-2022-49954 https://cve.radiocsirt.org/vuln/ghsa-vq44-q98p-r6hq <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>Input: iforce - wake up after clearing IFORCE_XMIT_RUNNING flag</p> <p>syzbot is reporting hung task at __input_unregister_device() [1], for iforce_close() waiting at wait_event_interruptible() with dev-&gt;mutex held is blocking input_disconnect_device() from __input_unregister_device().</p> <p>It seems that the cause is simply that commit c2b27ef672992a20 (&#34;Input: iforce - wait for command completion when closing the device&#34;) forgot to call wake_up() after clear_bit().</p> <p>Fix this problem by introducing a helper that calls clear_bit() followed by wake_up_all().</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>Input: iforce - wake up after clearing IFORCE_XMIT_RUNNING flag</p> <p>syzbot is reporting hung task at __input_unregister_device() [1], for iforce_close() waiting at wait_event_interruptible() with dev-&gt;mutex held is blocking input_disconnect_device() from __input_unregister_device().</p> <p>It seems that the cause is simply that commit c2b27ef672992a20 (&#34;Input: iforce - wait for command completion when closing the device&#34;) forgot to call wake_up() after clear_bit().</p> <p>Fix this problem by introducing a helper that calls clear_bit() followed by wake_up_all().</p> https://cve.radiocsirt.org/vuln/ghsa-vq44-q98p-r6hq https://cve.radiocsirt.org/vuln/suse-su-2025:02264-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2025:02264-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49954 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 146 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: Input: iforce - wake up after clearing IFORCE_XMIT_RUNNING flag syzbot is reporting hung task at __input_unregister_device() [1], for iforce_close() waiting at wait_event_interruptible() with dev-&gt;mutex held is blocking input_disconnect_device() from __input_unregister_device(). It seems that the cause is simply that commit c2b27ef672992a20 (&#34;Input: iforce - wait for command completion when closing the device&#34;) forgot to call wake_up() after clear_bit(). Fix this problem by introducing a helper that calls clear_bit() followed by wake_up_all().</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 146 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: Input: iforce - wake up after clearing IFORCE_XMIT_RUNNING flag syzbot is reporting hung task at __input_unregister_device() [1], for iforce_close() waiting at wait_event_interruptible() with dev-&gt;mutex held is blocking input_disconnect_device() from __input_unregister_device(). It seems that the cause is simply that commit c2b27ef672992a20 (&#34;Input: iforce - wait for command completion when closing the device&#34;) forgot to call wake_up() after clear_bit(). Fix this problem by introducing a helper that calls clear_bit() followed by wake_up_all().</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49954 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1350 <p>Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.</p> <p>Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1350