https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 05 Oct 2026 10:24:25 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-13685 bdu:2025-13685 https://cve.radiocsirt.org/vuln/bdu:2025-13685 https://cve.radiocsirt.org/vuln/bell-cve-2025-39859 <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://cve.radiocsirt.org/vuln/bell-cve-2025-39859 https://cve.radiocsirt.org/vuln/certfr-2025-avi-1133 certfr-2025-avi-1133 https://cve.radiocsirt.org/vuln/certfr-2025-avi-1133 https://cve.radiocsirt.org/vuln/euvd-2026-314795 EUVD-2026-314795 https://cve.radiocsirt.org/vuln/euvd-2026-314795 https://cve.radiocsirt.org/vuln/fkie_cve-2025-39859 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ptp: ocp: fix use-after-free bugs causing by ptp_ocp_watchdog</p> <p>The ptp_ocp_detach() only shuts down the watchdog timer if it is pending. However, if the timer handler is already running, the timer_delete_sync() is not called. This leads to race conditions where the devlink that contains the ptp_ocp is deallocated while the timer handler is still accessing it, resulting in use-after-free bugs. The following details one of the race scenarios.</p> <p>(thread 1) | (thread 2) ptp_ocp_remove() | ptp_ocp_detach() | ptp_ocp_watchdog() if (timer_pending(&amp;bp-&gt;watchdog))| bp = timer_container_of() timer_delete_sync() | | devlink_free(devlink) //free | | bp-&gt; //use</p> <p>Resolve this by unconditionally calling timer_delete_sync() to ensure the timer is reliably deactivated, preventing any access after free.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ptp: ocp: fix use-after-free bugs causing by ptp_ocp_watchdog</p> <p>The ptp_ocp_detach() only shuts down the watchdog timer if it is pending. However, if the timer handler is already running, the timer_delete_sync() is not called. This leads to race conditions where the devlink that contains the ptp_ocp is deallocated while the timer handler is still accessing it, resulting in use-after-free bugs. The following details one of the race scenarios.</p> <p>(thread 1) | (thread 2) ptp_ocp_remove() | ptp_ocp_detach() | ptp_ocp_watchdog() if (timer_pending(&amp;bp-&gt;watchdog))| bp = timer_container_of() timer_delete_sync() | | devlink_free(devlink) //free | | bp-&gt; //use</p> <p>Resolve this by unconditionally calling timer_delete_sync() to ensure the timer is reliably deactivated, preventing any access after free.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-39859 https://cve.radiocsirt.org/vuln/ghsa-fq5x-p5vr-m6pg <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ptp: ocp: fix use-after-free bugs causing by ptp_ocp_watchdog</p> <p>The ptp_ocp_detach() only shuts down the watchdog timer if it is pending. However, if the timer handler is already running, the timer_delete_sync() is not called. This leads to race conditions where the devlink that contains the ptp_ocp is deallocated while the timer handler is still accessing it, resulting in use-after-free bugs. The following details one of the race scenarios.</p> <p>(thread 1) | (thread 2) ptp_ocp_remove() | ptp_ocp_detach() | ptp_ocp_watchdog() if (timer_pending(&amp;bp-&gt;watchdog))| bp = timer_container_of() timer_delete_sync() | | devlink_free(devlink) //free | | bp-&gt; //use</p> <p>Resolve this by unconditionally calling timer_delete_sync() to ensure the timer is reliably deactivated, preventing any access after free.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ptp: ocp: fix use-after-free bugs causing by ptp_ocp_watchdog</p> <p>The ptp_ocp_detach() only shuts down the watchdog timer if it is pending. However, if the timer handler is already running, the timer_delete_sync() is not called. This leads to race conditions where the devlink that contains the ptp_ocp is deallocated while the timer handler is still accessing it, resulting in use-after-free bugs. The following details one of the race scenarios.</p> <p>(thread 1) | (thread 2) ptp_ocp_remove() | ptp_ocp_detach() | ptp_ocp_watchdog() if (timer_pending(&amp;bp-&gt;watchdog))| bp = timer_container_of() timer_delete_sync() | | devlink_free(devlink) //free | | bp-&gt; //use</p> <p>Resolve this by unconditionally calling timer_delete_sync() to ensure the timer is reliably deactivated, preventing any access after free.</p> https://cve.radiocsirt.org/vuln/ghsa-fq5x-p5vr-m6pg https://cve.radiocsirt.org/vuln/msrc_cve-2025-39859 msrc_CVE-2025-39859 https://cve.radiocsirt.org/vuln/msrc_cve-2025-39859 https://cve.radiocsirt.org/vuln/opensuse-su-2025:20172-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/opensuse-su-2025:20172-1 https://cve.radiocsirt.org/vuln/suse-su-2025:4422-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:4422-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-39859 <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 164 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: ptp: ocp: fix use-after-free bugs causing by ptp_ocp_watchdog The ptp_ocp_detach() only shuts down the watchdog timer if it is pending. However, if the timer handler is already running, the timer_delete_sync() is not called. This leads to race conditions where the devlink that contains the ptp_ocp is deallocated while the timer handler is still accessing it, resulting in use-after-free bugs. The following details one of the race scenarios. (thread 1) | (thread 2) ptp_ocp_remove() | ptp_ocp_detach() | ptp_ocp_watchdog() if (timer_pending(&amp;bp-&gt;watchdog))| bp = timer_container_of() timer_delete_sync() | | devlink_free(devlink) //free | | bp-&gt; //use Resolve this by unconditionally calling timer_delete_sync() to ensure the timer is reliably deactivated, preventing any access after free.</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 164 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: ptp: ocp: fix use-after-free bugs causing by ptp_ocp_watchdog The ptp_ocp_detach() only shuts down the watchdog timer if it is pending. However, if the timer handler is already running, the timer_delete_sync() is not called. This leads to race conditions where the devlink that contains the ptp_ocp is deallocated while the timer handler is still accessing it, resulting in use-after-free bugs. The following details one of the race scenarios. (thread 1) | (thread 2) ptp_ocp_remove() | ptp_ocp_detach() | ptp_ocp_watchdog() if (timer_pending(&amp;bp-&gt;watchdog))| bp = timer_container_of() timer_delete_sync() | | devlink_free(devlink) //free | | bp-&gt; //use Resolve this by unconditionally calling timer_delete_sync() to ensure the timer is reliably deactivated, preventing any access after free.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-39859 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2099 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher beschriebene Auswirkungen zu erzielen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher beschriebene Auswirkungen zu erzielen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2099