https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 19:32:36 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-09297 bdu:2026-09297 https://cve.radiocsirt.org/vuln/bdu:2026-09297 https://cve.radiocsirt.org/vuln/bell-cve-2025-40296 <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2025-40296 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0169 certfr-2026-avi-0169 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0169 https://cve.radiocsirt.org/vuln/euvd-2026-314998 EUVD-2026-314998 https://cve.radiocsirt.org/vuln/euvd-2026-314998 https://cve.radiocsirt.org/vuln/fkie_cve-2025-40296 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>platform/x86: int3472: Fix double free of GPIO device during unregister</p> <p>regulator_unregister() already frees the associated GPIO device. On ThinkPad X9 (Lunar Lake), this causes a double free issue that leads to random failures when other drivers (typically Intel THC) attempt to allocate interrupts. The root cause is that the reference count of the pinctrl_intel_platform module unexpectedly drops to zero when this driver defers its probe.</p> <p>This behavior can also be reproduced by unloading the module directly.</p> <p>Fix the issue by removing the redundant release of the GPIO device during regulator unregistration.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>platform/x86: int3472: Fix double free of GPIO device during unregister</p> <p>regulator_unregister() already frees the associated GPIO device. On ThinkPad X9 (Lunar Lake), this causes a double free issue that leads to random failures when other drivers (typically Intel THC) attempt to allocate interrupts. The root cause is that the reference count of the pinctrl_intel_platform module unexpectedly drops to zero when this driver defers its probe.</p> <p>This behavior can also be reproduced by unloading the module directly.</p> <p>Fix the issue by removing the redundant release of the GPIO device during regulator unregistration.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-40296 https://cve.radiocsirt.org/vuln/ghsa-2g6j-xgp9-7mhx <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>platform/x86: int3472: Fix double free of GPIO device during unregister</p> <p>regulator_unregister() already frees the associated GPIO device. On ThinkPad X9 (Lunar Lake), this causes a double free issue that leads to random failures when other drivers (typically Intel THC) attempt to allocate interrupts. The root cause is that the reference count of the pinctrl_intel_platform module unexpectedly drops to zero when this driver defers its probe.</p> <p>This behavior can also be reproduced by unloading the module directly.</p> <p>Fix the issue by removing the redundant release of the GPIO device during regulator unregistration.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>platform/x86: int3472: Fix double free of GPIO device during unregister</p> <p>regulator_unregister() already frees the associated GPIO device. On ThinkPad X9 (Lunar Lake), this causes a double free issue that leads to random failures when other drivers (typically Intel THC) attempt to allocate interrupts. The root cause is that the reference count of the pinctrl_intel_platform module unexpectedly drops to zero when this driver defers its probe.</p> <p>This behavior can also be reproduced by unloading the module directly.</p> <p>Fix the issue by removing the redundant release of the GPIO device during regulator unregistration.</p> https://cve.radiocsirt.org/vuln/ghsa-2g6j-xgp9-7mhx https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-40296 <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 94 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: platform/x86: int3472: Fix double free of GPIO device during unregister regulator_unregister() already frees the associated GPIO device. On ThinkPad X9 (Lunar Lake), this causes a double free issue that leads to random failures when other drivers (typically Intel THC) attempt to allocate interrupts. The root cause is that the reference count of the pinctrl_intel_platform module unexpectedly drops to zero when this driver defers its probe. This behavior can also be reproduced by unloading the module directly. Fix the issue by removing the redundant release of the GPIO device during regulator unregistration.</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 94 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: platform/x86: int3472: Fix double free of GPIO device during unregister regulator_unregister() already frees the associated GPIO device. On ThinkPad X9 (Lunar Lake), this causes a double free issue that leads to random failures when other drivers (typically Intel THC) attempt to allocate interrupts. The root cause is that the reference count of the pinctrl_intel_platform module unexpectedly drops to zero when this driver defers its probe. This behavior can also be reproduced by unloading the module directly. Fix the issue by removing the redundant release of the GPIO device during regulator unregistration.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-40296 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2756 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder weitere, nicht spezifizierte Auswirkungen zu erlangen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder weitere, nicht spezifizierte Auswirkungen zu erlangen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2756