https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 05 Oct 2026 09:09:50 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-03684 bdu:2026-03684 https://cve.radiocsirt.org/vuln/bdu:2026-03684 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0252 certfr-2025-avi-0252 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0252 https://cve.radiocsirt.org/vuln/euvd-2026-344756 EUVD-2026-344756 https://cve.radiocsirt.org/vuln/euvd-2026-344756 https://cve.radiocsirt.org/vuln/fkie_cve-2022-49555 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>Bluetooth: hci_qca: Use del_timer_sync() before freeing</p> <p>While looking at a crash report on a timer list being corrupted, which usually happens when a timer is freed while still active. This is commonly triggered by code calling del_timer() instead of del_timer_sync() just before freeing.</p> <p>One possible culprit is the hci_qca driver, which does exactly that.</p> <p>Eric mentioned that wake_retrans_timer could be rearmed via the work queue, so also move the destruction of the work queue before del_timer_sync().</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>Bluetooth: hci_qca: Use del_timer_sync() before freeing</p> <p>While looking at a crash report on a timer list being corrupted, which usually happens when a timer is freed while still active. This is commonly triggered by code calling del_timer() instead of del_timer_sync() just before freeing.</p> <p>One possible culprit is the hci_qca driver, which does exactly that.</p> <p>Eric mentioned that wake_retrans_timer could be rearmed via the work queue, so also move the destruction of the work queue before del_timer_sync().</p> https://cve.radiocsirt.org/vuln/fkie_cve-2022-49555 https://cve.radiocsirt.org/vuln/ghsa-x3w4-q7cr-j86p <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>Bluetooth: hci_qca: Use del_timer_sync() before freeing</p> <p>While looking at a crash report on a timer list being corrupted, which usually happens when a timer is freed while still active. This is commonly triggered by code calling del_timer() instead of del_timer_sync() just before freeing.</p> <p>One possible culprit is the hci_qca driver, which does exactly that.</p> <p>Eric mentioned that wake_retrans_timer could be rearmed via the work queue, so also move the destruction of the work queue before del_timer_sync().</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>Bluetooth: hci_qca: Use del_timer_sync() before freeing</p> <p>While looking at a crash report on a timer list being corrupted, which usually happens when a timer is freed while still active. This is commonly triggered by code calling del_timer() instead of del_timer_sync() just before freeing.</p> <p>One possible culprit is the hci_qca driver, which does exactly that.</p> <p>Eric mentioned that wake_retrans_timer could be rearmed via the work queue, so also move the destruction of the work queue before del_timer_sync().</p> https://cve.radiocsirt.org/vuln/ghsa-x3w4-q7cr-j86p https://cve.radiocsirt.org/vuln/suse-su-2025:1176-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:1176-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49555 <p><strong>Affected:</strong> 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, Ubuntu:16.04:LTS: linux-hwe-edge and 143 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_qca: Use del_timer_sync() before freeing While looking at a crash report on a timer list being corrupted, which usually happens when a timer is freed while still active. This is commonly triggered by code calling del_timer() instead of del_timer_sync() just before freeing. One possible culprit is the hci_qca driver, which does exactly that. Eric mentioned that wake_retrans_timer could be rearmed via the work queue, so also move the destruction of the work queue before del_timer_sync().</p> <p><strong>Affected:</strong> 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, Ubuntu:16.04:LTS: linux-hwe-edge and 143 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_qca: Use del_timer_sync() before freeing While looking at a crash report on a timer list being corrupted, which usually happens when a timer is freed while still active. This is commonly triggered by code calling del_timer() instead of del_timer_sync() just before freeing. One possible culprit is the hci_qca driver, which does exactly that. Eric mentioned that wake_retrans_timer could be rearmed via the work queue, so also move the destruction of the work queue before del_timer_sync().</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49555