<?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>Sun, 04 Oct 2026 07:17:30 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-40347</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-40347</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2025-40347</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0108 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0108</link>
      <description>certfr-2026-avi-0108</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0108</guid>
    </item>
    <item>
      <title>EUVD-2026-347438</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-347438</link>
      <description>EUVD-2026-347438</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-347438</guid>
    </item>
    <item>
      <title>fkie_cve-2025-40347</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-40347</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: enetc: fix the deadlock of enetc_mdio_lock&lt;/p&gt;
&lt;p&gt;After applying the workaround for err050089, the LS1028A platform
experiences RCU stalls on RT kernel. This issue is caused by the
recursive acquisition of the read lock enetc_mdio_lock. Here list some
of the call stacks identified under the enetc_poll path that may lead to
a deadlock:&lt;/p&gt;
&lt;p&gt;enetc_poll
  -&amp;gt; enetc_lock_mdio
  -&amp;gt; enetc_clean_rx_ring OR napi_complete_done
     -&amp;gt; napi_gro_receive
        -&amp;gt; enetc_start_xmit
           -&amp;gt; enetc_lock_mdio
           -&amp;gt; enetc_map_tx_buffs
           -&amp;gt; enetc_unlock_mdio
  -&amp;gt; enetc_unlock_mdio&lt;/p&gt;
&lt;p&gt;After enetc_poll acquires the read lock, a higher-priority writer attempts
to acquire the lock, causing preemption. The writer detects that a
read lock is already held and is scheduled out. However, readers under
enetc_poll cannot acquire the read lock again because a writer is already
waiting, leading to a thread hang.&lt;/p&gt;
&lt;p&gt;Currently, the deadlock is avoided by adjusting enetc_lock_mdio to prevent
recursive lock acquisition.&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: enetc: fix the deadlock of enetc_mdio_lock&lt;/p&gt;
&lt;p&gt;After applying the workaround for err050089, the LS1028A platform
experiences RCU stalls on RT kernel. This issue is caused by the
recursive acquisition of the read lock enetc_mdio_lock. Here list some
of the call stacks identified under the enetc_poll path that may lead to
a deadlock:&lt;/p&gt;
&lt;p&gt;enetc_poll
  -&amp;gt; enetc_lock_mdio
  -&amp;gt; enetc_clean_rx_ring OR napi_complete_done
     -&amp;gt; napi_gro_receive
        -&amp;gt; enetc_start_xmit
           -&amp;gt; enetc_lock_mdio
           -&amp;gt; enetc_map_tx_buffs
           -&amp;gt; enetc_unlock_mdio
  -&amp;gt; enetc_unlock_mdio&lt;/p&gt;
&lt;p&gt;After enetc_poll acquires the read lock, a higher-priority writer attempts
to acquire the lock, causing preemption. The writer detects that a
read lock is already held and is scheduled out. However, readers under
enetc_poll cannot acquire the read lock again because a writer is already
waiting, leading to a thread hang.&lt;/p&gt;
&lt;p&gt;Currently, the deadlock is avoided by adjusting enetc_lock_mdio to prevent
recursive lock acquisition.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-40347</guid>
    </item>
    <item>
      <title>GHSA-r9fm-4g8c-9hfh</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-r9fm-4g8c-9hfh</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: enetc: fix the deadlock of enetc_mdio_lock&lt;/p&gt;
&lt;p&gt;After applying the workaround for err050089, the LS1028A platform
experiences RCU stalls on RT kernel. This issue is caused by the
recursive acquisition of the read lock enetc_mdio_lock. Here list some
of the call stacks identified under the enetc_poll path that may lead to
a deadlock:&lt;/p&gt;
&lt;p&gt;enetc_poll
  -&amp;gt; enetc_lock_mdio
  -&amp;gt; enetc_clean_rx_ring OR napi_complete_done
     -&amp;gt; napi_gro_receive
        -&amp;gt; enetc_start_xmit
           -&amp;gt; enetc_lock_mdio
           -&amp;gt; enetc_map_tx_buffs
           -&amp;gt; enetc_unlock_mdio
  -&amp;gt; enetc_unlock_mdio&lt;/p&gt;
&lt;p&gt;After enetc_poll acquires the read lock, a higher-priority writer attempts
to acquire the lock, causing preemption. The writer detects that a
read lock is already held and is scheduled out. However, readers under
enetc_poll cannot acquire the read lock again because a writer is already
waiting, leading to a thread hang.&lt;/p&gt;
&lt;p&gt;Currently, the deadlock is avoided by adjusting enetc_lock_mdio to prevent
recursive lock acquisition.&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: enetc: fix the deadlock of enetc_mdio_lock&lt;/p&gt;
&lt;p&gt;After applying the workaround for err050089, the LS1028A platform
experiences RCU stalls on RT kernel. This issue is caused by the
recursive acquisition of the read lock enetc_mdio_lock. Here list some
of the call stacks identified under the enetc_poll path that may lead to
a deadlock:&lt;/p&gt;
&lt;p&gt;enetc_poll
  -&amp;gt; enetc_lock_mdio
  -&amp;gt; enetc_clean_rx_ring OR napi_complete_done
     -&amp;gt; napi_gro_receive
        -&amp;gt; enetc_start_xmit
           -&amp;gt; enetc_lock_mdio
           -&amp;gt; enetc_map_tx_buffs
           -&amp;gt; enetc_unlock_mdio
  -&amp;gt; enetc_unlock_mdio&lt;/p&gt;
&lt;p&gt;After enetc_poll acquires the read lock, a higher-priority writer attempts
to acquire the lock, causing preemption. The writer detects that a
read lock is already held and is scheduled out. However, readers under
enetc_poll cannot acquire the read lock again because a writer is already
waiting, leading to a thread hang.&lt;/p&gt;
&lt;p&gt;Currently, the deadlock is avoided by adjusting enetc_lock_mdio to prevent
recursive lock acquisition.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-r9fm-4g8c-9hfh</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:20145-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:20145-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:20145-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:0278-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:0278-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2026:0278-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-40347</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-40347</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 176 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: enetc: fix the deadlock of enetc_mdio_lock After applying the workaround for err050089, the LS1028A platform experiences RCU stalls on RT kernel. This issue is caused by the recursive acquisition of the read lock enetc_mdio_lock. Here list some of the call stacks identified under the enetc_poll path that may lead to a deadlock: enetc_poll   -&amp;gt; enetc_lock_mdio   -&amp;gt; enetc_clean_rx_ring OR napi_complete_done      -&amp;gt; napi_gro_receive         -&amp;gt; enetc_start_xmit            -&amp;gt; enetc_lock_mdio            -&amp;gt; enetc_map_tx_buffs            -&amp;gt; enetc_unlock_mdio   -&amp;gt; enetc_unlock_mdio After enetc_poll acquires the read lock, a higher-priority writer attempts to acquire the lock, causing preemption. The writer detects that a read lock is already held and is scheduled out. However, readers under enetc_poll cannot acquire the read lock again because a writer is already waiting, leading to a thread hang. Currently, the deadlock is avoided by adjusting enetc_lock_mdio to prevent recursive lock acquisition.&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 176 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: enetc: fix the deadlock of enetc_mdio_lock After applying the workaround for err050089, the LS1028A platform experiences RCU stalls on RT kernel. This issue is caused by the recursive acquisition of the read lock enetc_mdio_lock. Here list some of the call stacks identified under the enetc_poll path that may lead to a deadlock: enetc_poll   -&amp;gt; enetc_lock_mdio   -&amp;gt; enetc_clean_rx_ring OR napi_complete_done      -&amp;gt; napi_gro_receive         -&amp;gt; enetc_start_xmit            -&amp;gt; enetc_lock_mdio            -&amp;gt; enetc_map_tx_buffs            -&amp;gt; enetc_unlock_mdio   -&amp;gt; enetc_unlock_mdio After enetc_poll acquires the read lock, a higher-priority writer attempts to acquire the lock, causing preemption. The writer detects that a read lock is already held and is scheduled out. However, readers under enetc_poll cannot acquire the read lock again because a writer is already waiting, leading to a thread hang. Currently, the deadlock is avoided by adjusting enetc_lock_mdio to prevent recursive lock acquisition.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-40347</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2868 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2868</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2868</guid>
    </item>
  </channel>
</rss>
