<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 08 Oct 2026 14:51:20 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-02849</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-02849</link>
      <description>bdu:2026-02849</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-02849</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-38720</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-38720</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2025-38720</guid>
    </item>
    <item>
      <title>EUVD-2026-314728</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-314728</link>
      <description>EUVD-2026-314728</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-314728</guid>
    </item>
    <item>
      <title>fkie_cve-2025-38720</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-38720</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: hibmcge: fix rtnl deadlock issue&lt;/p&gt;
&lt;p&gt;Currently, the hibmcge netdev acquires the rtnl_lock in
pci_error_handlers.reset_prepare() and releases it in
pci_error_handlers.reset_done().&lt;/p&gt;
&lt;p&gt;However, in the PCI framework:
pci_reset_bus - __pci_reset_slot - pci_slot_save_and_disable_locked -
 pci_dev_save_and_disable - err_handler-&amp;gt;reset_prepare(dev);&lt;/p&gt;
&lt;p&gt;In pci_slot_save_and_disable_locked():
	list_for_each_entry(dev, &amp;amp;slot-&amp;gt;bus-&amp;gt;devices, bus_list) {
		if (!dev-&amp;gt;slot || dev-&amp;gt;slot!= slot)
			continue;
		pci_dev_save_and_disable(dev);
		if (dev-&amp;gt;subordinate)
			pci_bus_save_and_disable_locked(dev-&amp;gt;subordinate);
	}&lt;/p&gt;
&lt;p&gt;This will iterate through all devices under the current bus and execute
err_handler-&amp;gt;reset_prepare(), causing two devices of the hibmcge driver
to sequentially request the rtnl_lock, leading to a deadlock.&lt;/p&gt;
&lt;p&gt;Since the driver now executes netif_device_detach()
before the reset process, it will not concurrently with
other netdev APIs, so there is no need to hold the rtnl_lock now.&lt;/p&gt;
&lt;p&gt;Therefore, this patch removes the rtnl_lock during the reset process and
adjusts the position of HBG_NIC_STATE_RESETTING to ensure
that multiple resets are not executed concurrently.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: hibmcge: fix rtnl deadlock issue&lt;/p&gt;
&lt;p&gt;Currently, the hibmcge netdev acquires the rtnl_lock in
pci_error_handlers.reset_prepare() and releases it in
pci_error_handlers.reset_done().&lt;/p&gt;
&lt;p&gt;However, in the PCI framework:
pci_reset_bus - __pci_reset_slot - pci_slot_save_and_disable_locked -
 pci_dev_save_and_disable - err_handler-&amp;gt;reset_prepare(dev);&lt;/p&gt;
&lt;p&gt;In pci_slot_save_and_disable_locked():
	list_for_each_entry(dev, &amp;amp;slot-&amp;gt;bus-&amp;gt;devices, bus_list) {
		if (!dev-&amp;gt;slot || dev-&amp;gt;slot!= slot)
			continue;
		pci_dev_save_and_disable(dev);
		if (dev-&amp;gt;subordinate)
			pci_bus_save_and_disable_locked(dev-&amp;gt;subordinate);
	}&lt;/p&gt;
&lt;p&gt;This will iterate through all devices under the current bus and execute
err_handler-&amp;gt;reset_prepare(), causing two devices of the hibmcge driver
to sequentially request the rtnl_lock, leading to a deadlock.&lt;/p&gt;
&lt;p&gt;Since the driver now executes netif_device_detach()
before the reset process, it will not concurrently with
other netdev APIs, so there is no need to hold the rtnl_lock now.&lt;/p&gt;
&lt;p&gt;Therefore, this patch removes the rtnl_lock during the reset process and
adjusts the position of HBG_NIC_STATE_RESETTING to ensure
that multiple resets are not executed concurrently.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-38720</guid>
    </item>
    <item>
      <title>GHSA-4457-8q65-98hw</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-4457-8q65-98hw</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: hibmcge: fix rtnl deadlock issue&lt;/p&gt;
&lt;p&gt;Currently, the hibmcge netdev acquires the rtnl_lock in
pci_error_handlers.reset_prepare() and releases it in
pci_error_handlers.reset_done().&lt;/p&gt;
&lt;p&gt;However, in the PCI framework:
pci_reset_bus - __pci_reset_slot - pci_slot_save_and_disable_locked -
 pci_dev_save_and_disable - err_handler-&amp;gt;reset_prepare(dev);&lt;/p&gt;
&lt;p&gt;In pci_slot_save_and_disable_locked():
	list_for_each_entry(dev, &amp;amp;slot-&amp;gt;bus-&amp;gt;devices, bus_list) {
		if (!dev-&amp;gt;slot || dev-&amp;gt;slot!= slot)
			continue;
		pci_dev_save_and_disable(dev);
		if (dev-&amp;gt;subordinate)
			pci_bus_save_and_disable_locked(dev-&amp;gt;subordinate);
	}&lt;/p&gt;
&lt;p&gt;This will iterate through all devices under the current bus and execute
err_handler-&amp;gt;reset_prepare(), causing two devices of the hibmcge driver
to sequentially request the rtnl_lock, leading to a deadlock.&lt;/p&gt;
&lt;p&gt;Since the driver now executes netif_device_detach()
before the reset process, it will not concurrently with
other netdev APIs, so there is no need to hold the rtnl_lock now.&lt;/p&gt;
&lt;p&gt;Therefore, this patch removes the rtnl_lock during the reset process and
adjusts the position of HBG_NIC_STATE_RESETTING to ensure
that multiple resets are not executed concurrently.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: hibmcge: fix rtnl deadlock issue&lt;/p&gt;
&lt;p&gt;Currently, the hibmcge netdev acquires the rtnl_lock in
pci_error_handlers.reset_prepare() and releases it in
pci_error_handlers.reset_done().&lt;/p&gt;
&lt;p&gt;However, in the PCI framework:
pci_reset_bus - __pci_reset_slot - pci_slot_save_and_disable_locked -
 pci_dev_save_and_disable - err_handler-&amp;gt;reset_prepare(dev);&lt;/p&gt;
&lt;p&gt;In pci_slot_save_and_disable_locked():
	list_for_each_entry(dev, &amp;amp;slot-&amp;gt;bus-&amp;gt;devices, bus_list) {
		if (!dev-&amp;gt;slot || dev-&amp;gt;slot!= slot)
			continue;
		pci_dev_save_and_disable(dev);
		if (dev-&amp;gt;subordinate)
			pci_bus_save_and_disable_locked(dev-&amp;gt;subordinate);
	}&lt;/p&gt;
&lt;p&gt;This will iterate through all devices under the current bus and execute
err_handler-&amp;gt;reset_prepare(), causing two devices of the hibmcge driver
to sequentially request the rtnl_lock, leading to a deadlock.&lt;/p&gt;
&lt;p&gt;Since the driver now executes netif_device_detach()
before the reset process, it will not concurrently with
other netdev APIs, so there is no need to hold the rtnl_lock now.&lt;/p&gt;
&lt;p&gt;Therefore, this patch removes the rtnl_lock during the reset process and
adjusts the position of HBG_NIC_STATE_RESETTING to ensure
that multiple resets are not executed concurrently.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-4457-8q65-98hw</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38720</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38720</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 88 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: hibmcge: fix rtnl deadlock issue Currently, the hibmcge netdev acquires the rtnl_lock in pci_error_handlers.reset_prepare() and releases it in pci_error_handlers.reset_done(). However, in the PCI framework: pci_reset_bus - __pci_reset_slot - pci_slot_save_and_disable_locked -  pci_dev_save_and_disable - err_handler-&amp;gt;reset_prepare(dev); In pci_slot_save_and_disable_locked(): 	list_for_each_entry(dev, &amp;amp;slot-&amp;gt;bus-&amp;gt;devices, bus_list) { 		if (!dev-&amp;gt;slot || dev-&amp;gt;slot!= slot) 			continue; 		pci_dev_save_and_disable(dev); 		if (dev-&amp;gt;subordinate) 			pci_bus_save_and_disable_locked(dev-&amp;gt;subordinate); 	} This will iterate through all devices under the current bus and execute err_handler-&amp;gt;reset_prepare(), causing two devices of the hibmcge driver to sequentially request the rtnl_lock, leading to a deadlock. Since the driver now executes netif_device_detach() before the reset process, it will not concurrently with other netdev APIs, so there is no need to hold the rtnl_lock now. Therefore, this patch removes the rtnl_lock during the reset process and adjusts the position of HBG_NIC_STATE_RESETTING to ensure that multiple resets are not executed concurrently.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 88 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: hibmcge: fix rtnl deadlock issue Currently, the hibmcge netdev acquires the rtnl_lock in pci_error_handlers.reset_prepare() and releases it in pci_error_handlers.reset_done(). However, in the PCI framework: pci_reset_bus - __pci_reset_slot - pci_slot_save_and_disable_locked -  pci_dev_save_and_disable - err_handler-&amp;gt;reset_prepare(dev); In pci_slot_save_and_disable_locked(): 	list_for_each_entry(dev, &amp;amp;slot-&amp;gt;bus-&amp;gt;devices, bus_list) { 		if (!dev-&amp;gt;slot || dev-&amp;gt;slot!= slot) 			continue; 		pci_dev_save_and_disable(dev); 		if (dev-&amp;gt;subordinate) 			pci_bus_save_and_disable_locked(dev-&amp;gt;subordinate); 	} This will iterate through all devices under the current bus and execute err_handler-&amp;gt;reset_prepare(), causing two devices of the hibmcge driver to sequentially request the rtnl_lock, leading to a deadlock. Since the driver now executes netif_device_detach() before the reset process, it will not concurrently with other netdev APIs, so there is no need to hold the rtnl_lock now. Therefore, this patch removes the rtnl_lock during the reset process and adjusts the position of HBG_NIC_STATE_RESETTING to ensure that multiple resets are not executed concurrently.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38720</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-1976 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1976</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder andere nicht spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder andere nicht spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1976</guid>
    </item>
  </channel>
</rss>
