https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 19:42:54 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-15789 bdu:2025-15789 https://cve.radiocsirt.org/vuln/bdu:2025-15789 https://cve.radiocsirt.org/vuln/bell-cve-2025-38623 <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-38623 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0894 certfr-2025-avi-0894 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0894 https://cve.radiocsirt.org/vuln/euvd-2026-314683 EUVD-2026-314683 https://cve.radiocsirt.org/vuln/euvd-2026-314683 https://cve.radiocsirt.org/vuln/fkie_cve-2025-38623 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>PCI: pnv_php: Fix surprise plug detection and recovery</p> <p>The existing PowerNV hotplug code did not handle surprise plug events correctly, leading to a complete failure of the hotplug system after device removal and a required reboot to detect new devices.</p> <p>This comes down to two issues:</p> <p>1) When a device is surprise removed, often the bridge upstream port will cause a PE freeze on the PHB. If this freeze is not cleared, the MSI interrupts from the bridge hotplug notification logic will not be received by the kernel, stalling all plug events on all slots associated with the PE.</p> <p>2) When a device is removed from a slot, regardless of surprise or programmatic removal, the associated PHB/PE ls left frozen. If this freeze is not cleared via a fundamental reset, skiboot is unable to clear the freeze and cannot retrain / rescan the slot. This also requires a reboot to clear the freeze and redetect the device in the slot.</p> <p>Issue the appropriate unfreeze and rescan commands on hotplug events, and don&#39;t oops on hotplug if pci_bus_to_OF_node() returns NULL.</p> <p>[bhelgaas: tidy comments]</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>PCI: pnv_php: Fix surprise plug detection and recovery</p> <p>The existing PowerNV hotplug code did not handle surprise plug events correctly, leading to a complete failure of the hotplug system after device removal and a required reboot to detect new devices.</p> <p>This comes down to two issues:</p> <p>1) When a device is surprise removed, often the bridge upstream port will cause a PE freeze on the PHB. If this freeze is not cleared, the MSI interrupts from the bridge hotplug notification logic will not be received by the kernel, stalling all plug events on all slots associated with the PE.</p> <p>2) When a device is removed from a slot, regardless of surprise or programmatic removal, the associated PHB/PE ls left frozen. If this freeze is not cleared via a fundamental reset, skiboot is unable to clear the freeze and cannot retrain / rescan the slot. This also requires a reboot to clear the freeze and redetect the device in the slot.</p> <p>Issue the appropriate unfreeze and rescan commands on hotplug events, and don&#39;t oops on hotplug if pci_bus_to_OF_node() returns NULL.</p> <p>[bhelgaas: tidy comments]</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-38623 https://cve.radiocsirt.org/vuln/ghsa-jm3q-7w4m-jc2w <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>PCI: pnv_php: Fix surprise plug detection and recovery</p> <p>The existing PowerNV hotplug code did not handle surprise plug events correctly, leading to a complete failure of the hotplug system after device removal and a required reboot to detect new devices.</p> <p>This comes down to two issues:</p> <p>1) When a device is surprise removed, often the bridge upstream port will cause a PE freeze on the PHB. If this freeze is not cleared, the MSI interrupts from the bridge hotplug notification logic will not be received by the kernel, stalling all plug events on all slots associated with the PE.</p> <p>2) When a device is removed from a slot, regardless of surprise or programmatic removal, the associated PHB/PE ls left frozen. If this freeze is not cleared via a fundamental reset, skiboot is unable to clear the freeze and cannot retrain / rescan the slot. This also requires a reboot to clear the freeze and redetect the device in the slot.</p> <p>Issue the appropriate unfreeze and rescan commands on hotplug events, and don&#39;t oops on hotplug if pci_bus_to_OF_node() returns NULL.</p> <p>[bhelgaas: tidy comments]</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>PCI: pnv_php: Fix surprise plug detection and recovery</p> <p>The existing PowerNV hotplug code did not handle surprise plug events correctly, leading to a complete failure of the hotplug system after device removal and a required reboot to detect new devices.</p> <p>This comes down to two issues:</p> <p>1) When a device is surprise removed, often the bridge upstream port will cause a PE freeze on the PHB. If this freeze is not cleared, the MSI interrupts from the bridge hotplug notification logic will not be received by the kernel, stalling all plug events on all slots associated with the PE.</p> <p>2) When a device is removed from a slot, regardless of surprise or programmatic removal, the associated PHB/PE ls left frozen. If this freeze is not cleared via a fundamental reset, skiboot is unable to clear the freeze and cannot retrain / rescan the slot. This also requires a reboot to clear the freeze and redetect the device in the slot.</p> <p>Issue the appropriate unfreeze and rescan commands on hotplug events, and don&#39;t oops on hotplug if pci_bus_to_OF_node() returns NULL.</p> <p>[bhelgaas: tidy comments]</p> https://cve.radiocsirt.org/vuln/ghsa-jm3q-7w4m-jc2w https://cve.radiocsirt.org/vuln/msrc_cve-2025-38623 msrc_CVE-2025-38623 https://cve.radiocsirt.org/vuln/msrc_cve-2025-38623 https://cve.radiocsirt.org/vuln/opensuse-su-2025:20081-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:20081-1 https://cve.radiocsirt.org/vuln/suse-su-2025:03600-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:03600-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38623 <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 215 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: PCI: pnv_php: Fix surprise plug detection and recovery The existing PowerNV hotplug code did not handle surprise plug events correctly, leading to a complete failure of the hotplug system after device removal and a required reboot to detect new devices. This comes down to two issues: 1) When a device is surprise removed, often the bridge upstream port will cause a PE freeze on the PHB. If this freeze is not cleared, the MSI interrupts from the bridge hotplug notification logic will not be received by the kernel, stalling all plug events on all slots associated with the PE. 2) When a device is removed from a slot, regardless of surprise or programmatic removal, the associated PHB/PE ls left frozen. If this freeze is not cleared via a fundamental reset, skiboot is unable to clear the freeze and cannot retrain / rescan the slot. This also requires a reboot to clear the freeze and redetect the device in the slot. Issue the appropriate unfreeze and rescan commands on hotplug events, and don&#39;t oops on hotplug if pci_bus_to_OF_node() returns NULL. [bhelgaas: tidy comments]</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 215 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: PCI: pnv_php: Fix surprise plug detection and recovery The existing PowerNV hotplug code did not handle surprise plug events correctly, leading to a complete failure of the hotplug system after device removal and a required reboot to detect new devices. This comes down to two issues: 1) When a device is surprise removed, often the bridge upstream port will cause a PE freeze on the PHB. If this freeze is not cleared, the MSI interrupts from the bridge hotplug notification logic will not be received by the kernel, stalling all plug events on all slots associated with the PE. 2) When a device is removed from a slot, regardless of surprise or programmatic removal, the associated PHB/PE ls left frozen. If this freeze is not cleared via a fundamental reset, skiboot is unable to clear the freeze and cannot retrain / rescan the slot. This also requires a reboot to clear the freeze and redetect the device in the slot. Issue the appropriate unfreeze and rescan commands on hotplug events, and don&#39;t oops on hotplug if pci_bus_to_OF_node() returns NULL. [bhelgaas: tidy comments]</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38623 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1898 <p>Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen, um seine Privilegien zu erhöhen oder andere nicht spezifizierte Angriffe durchzuführen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen, um seine Privilegien zu erhöhen oder andere nicht spezifizierte Angriffe durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1898