https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 30 Sep 2026 08:28:24 +0000 https://vulnerability.circl.lu/vuln/bell-cve-2026-80572 <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://vulnerability.circl.lu/vuln/bell-cve-2026-80572 https://vulnerability.circl.lu/vuln/certfr-2026-avi-1119 certfr-2026-avi-1119 https://vulnerability.circl.lu/vuln/certfr-2026-avi-1119 https://vulnerability.circl.lu/vuln/fkie_cve-2026-80572 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>Input: byd - synchronize timer deletion before freeing private data</p> <p>byd_disconnect() uses timer_delete() before freeing the driver&#39;s private data. This does not wait for a running byd_clear_touch() callback, which dereferences the private data and its psmouse pointer. A callback racing with disconnect can therefore access the private data after it has been freed. The timer can also still be re-armed by byd_process_byte() while the disconnect is in progress.</p> <p>Use timer_shutdown_sync() before freeing the private data: it waits for a running callback and turns any later re-arm attempt into a no-op.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>Input: byd - synchronize timer deletion before freeing private data</p> <p>byd_disconnect() uses timer_delete() before freeing the driver&#39;s private data. This does not wait for a running byd_clear_touch() callback, which dereferences the private data and its psmouse pointer. A callback racing with disconnect can therefore access the private data after it has been freed. The timer can also still be re-armed by byd_process_byte() while the disconnect is in progress.</p> <p>Use timer_shutdown_sync() before freeing the private data: it waits for a running callback and turns any later re-arm attempt into a no-op.</p> https://vulnerability.circl.lu/vuln/fkie_cve-2026-80572 https://vulnerability.circl.lu/vuln/ghsa-g6j6-j6hv-j2v2 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>Input: byd - synchronize timer deletion before freeing private data</p> <p>byd_disconnect() uses timer_delete() before freeing the driver&#39;s private data. This does not wait for a running byd_clear_touch() callback, which dereferences the private data and its psmouse pointer. A callback racing with disconnect can therefore access the private data after it has been freed. The timer can also still be re-armed by byd_process_byte() while the disconnect is in progress.</p> <p>Use timer_shutdown_sync() before freeing the private data: it waits for a running callback and turns any later re-arm attempt into a no-op.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>Input: byd - synchronize timer deletion before freeing private data</p> <p>byd_disconnect() uses timer_delete() before freeing the driver&#39;s private data. This does not wait for a running byd_clear_touch() callback, which dereferences the private data and its psmouse pointer. A callback racing with disconnect can therefore access the private data after it has been freed. The timer can also still be re-armed by byd_process_byte() while the disconnect is in progress.</p> <p>Use timer_shutdown_sync() before freeing the private data: it waits for a running callback and turns any later re-arm attempt into a no-op.</p> https://vulnerability.circl.lu/vuln/ghsa-g6j6-j6hv-j2v2 https://vulnerability.circl.lu/vuln/msrc_cve-2026-80572 msrc_CVE-2026-80572 https://vulnerability.circl.lu/vuln/msrc_cve-2026-80572 https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-80572 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 239 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: Input: byd - synchronize timer deletion before freeing private data byd_disconnect() uses timer_delete() before freeing the driver&#39;s private data. This does not wait for a running byd_clear_touch() callback, which dereferences the private data and its psmouse pointer. A callback racing with disconnect can therefore access the private data after it has been freed. The timer can also still be re-armed by byd_process_byte() while the disconnect is in progress. Use timer_shutdown_sync() before freeing the private data: it waits for a running callback and turns any later re-arm attempt into a no-op.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 239 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: Input: byd - synchronize timer deletion before freeing private data byd_disconnect() uses timer_delete() before freeing the driver&#39;s private data. This does not wait for a running byd_clear_touch() callback, which dereferences the private data and its psmouse pointer. A callback racing with disconnect can therefore access the private data after it has been freed. The timer can also still be re-armed by byd_process_byte() while the disconnect is in progress. Use timer_shutdown_sync() before freeing the private data: it waits for a running callback and turns any later re-arm attempt into a no-op.</p> https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-80572