<?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 09:34:40 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-12159</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-12159</link>
      <description>bdu:2026-12159</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-12159</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-23188</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-23188</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-23188</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0192 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0192</link>
      <description>certfr-2026-avi-0192</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0192</guid>
    </item>
    <item>
      <title>EUVD-2026-315398</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-315398</link>
      <description>EUVD-2026-315398</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-315398</guid>
    </item>
    <item>
      <title>fkie_cve-2026-23188</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-23188</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: usb: r8152: fix resume reset deadlock&lt;/p&gt;
&lt;p&gt;rtl8152 can trigger device reset during reset which
potentially can result in a deadlock:&lt;/p&gt;
&lt;p&gt;**** DPM device timeout after 10 seconds; 15 seconds until panic ****
 Call Trace:
 &amp;lt;TASK&amp;gt;
 schedule+0x483/0x1370
 schedule_preempt_disabled+0x15/0x30
 __mutex_lock_common+0x1fd/0x470
 __rtl8152_set_mac_address+0x80/0x1f0
 dev_set_mac_address+0x7f/0x150
 rtl8152_post_reset+0x72/0x150
 usb_reset_device+0x1d0/0x220
 rtl8152_resume+0x99/0xc0
 usb_resume_interface+0x3e/0xc0
 usb_resume_both+0x104/0x150
 usb_resume+0x22/0x110&lt;/p&gt;
&lt;p&gt;The problem is that rtl8152 resume calls reset under
tp-&amp;gt;control mutex while reset basically re-enters rtl8152
and attempts to acquire the same tp-&amp;gt;control lock once
again.&lt;/p&gt;
&lt;p&gt;Reset INACCESSIBLE device outside of tp-&amp;gt;control mutex
scope to avoid recursive mutex_lock() deadlock.&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: usb: r8152: fix resume reset deadlock&lt;/p&gt;
&lt;p&gt;rtl8152 can trigger device reset during reset which
potentially can result in a deadlock:&lt;/p&gt;
&lt;p&gt;**** DPM device timeout after 10 seconds; 15 seconds until panic ****
 Call Trace:
 &amp;lt;TASK&amp;gt;
 schedule+0x483/0x1370
 schedule_preempt_disabled+0x15/0x30
 __mutex_lock_common+0x1fd/0x470
 __rtl8152_set_mac_address+0x80/0x1f0
 dev_set_mac_address+0x7f/0x150
 rtl8152_post_reset+0x72/0x150
 usb_reset_device+0x1d0/0x220
 rtl8152_resume+0x99/0xc0
 usb_resume_interface+0x3e/0xc0
 usb_resume_both+0x104/0x150
 usb_resume+0x22/0x110&lt;/p&gt;
&lt;p&gt;The problem is that rtl8152 resume calls reset under
tp-&amp;gt;control mutex while reset basically re-enters rtl8152
and attempts to acquire the same tp-&amp;gt;control lock once
again.&lt;/p&gt;
&lt;p&gt;Reset INACCESSIBLE device outside of tp-&amp;gt;control mutex
scope to avoid recursive mutex_lock() deadlock.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-23188</guid>
    </item>
    <item>
      <title>GHSA-hjjf-xjvr-567j</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-hjjf-xjvr-567j</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: usb: r8152: fix resume reset deadlock&lt;/p&gt;
&lt;p&gt;rtl8152 can trigger device reset during reset which
potentially can result in a deadlock:&lt;/p&gt;
&lt;p&gt;**** DPM device timeout after 10 seconds; 15 seconds until panic ****
 Call Trace:
 &amp;lt;TASK&amp;gt;
 schedule+0x483/0x1370
 schedule_preempt_disabled+0x15/0x30
 __mutex_lock_common+0x1fd/0x470
 __rtl8152_set_mac_address+0x80/0x1f0
 dev_set_mac_address+0x7f/0x150
 rtl8152_post_reset+0x72/0x150
 usb_reset_device+0x1d0/0x220
 rtl8152_resume+0x99/0xc0
 usb_resume_interface+0x3e/0xc0
 usb_resume_both+0x104/0x150
 usb_resume+0x22/0x110&lt;/p&gt;
&lt;p&gt;The problem is that rtl8152 resume calls reset under
tp-&amp;gt;control mutex while reset basically re-enters rtl8152
and attempts to acquire the same tp-&amp;gt;control lock once
again.&lt;/p&gt;
&lt;p&gt;Reset INACCESSIBLE device outside of tp-&amp;gt;control mutex
scope to avoid recursive mutex_lock() deadlock.&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: usb: r8152: fix resume reset deadlock&lt;/p&gt;
&lt;p&gt;rtl8152 can trigger device reset during reset which
potentially can result in a deadlock:&lt;/p&gt;
&lt;p&gt;**** DPM device timeout after 10 seconds; 15 seconds until panic ****
 Call Trace:
 &amp;lt;TASK&amp;gt;
 schedule+0x483/0x1370
 schedule_preempt_disabled+0x15/0x30
 __mutex_lock_common+0x1fd/0x470
 __rtl8152_set_mac_address+0x80/0x1f0
 dev_set_mac_address+0x7f/0x150
 rtl8152_post_reset+0x72/0x150
 usb_reset_device+0x1d0/0x220
 rtl8152_resume+0x99/0xc0
 usb_resume_interface+0x3e/0xc0
 usb_resume_both+0x104/0x150
 usb_resume+0x22/0x110&lt;/p&gt;
&lt;p&gt;The problem is that rtl8152 resume calls reset under
tp-&amp;gt;control mutex while reset basically re-enters rtl8152
and attempts to acquire the same tp-&amp;gt;control lock once
again.&lt;/p&gt;
&lt;p&gt;Reset INACCESSIBLE device outside of tp-&amp;gt;control mutex
scope to avoid recursive mutex_lock() deadlock.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-hjjf-xjvr-567j</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:20416-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:20416-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:20416-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:20838-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:20838-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:20838-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-23188</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23188</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 106 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: usb: r8152: fix resume reset deadlock rtl8152 can trigger device reset during reset which potentially can result in a deadlock:  **** DPM device timeout after 10 seconds; 15 seconds until panic ****  Call Trace:  &amp;lt;TASK&amp;gt;  schedule+0x483/0x1370  schedule_preempt_disabled+0x15/0x30  __mutex_lock_common+0x1fd/0x470  __rtl8152_set_mac_address+0x80/0x1f0  dev_set_mac_address+0x7f/0x150  rtl8152_post_reset+0x72/0x150  usb_reset_device+0x1d0/0x220  rtl8152_resume+0x99/0xc0  usb_resume_interface+0x3e/0xc0  usb_resume_both+0x104/0x150  usb_resume+0x22/0x110 The problem is that rtl8152 resume calls reset under tp-&amp;gt;control mutex while reset basically re-enters rtl8152 and attempts to acquire the same tp-&amp;gt;control lock once again. Reset INACCESSIBLE device outside of tp-&amp;gt;control mutex scope to avoid recursive mutex_lock() deadlock.&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 106 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: usb: r8152: fix resume reset deadlock rtl8152 can trigger device reset during reset which potentially can result in a deadlock:  **** DPM device timeout after 10 seconds; 15 seconds until panic ****  Call Trace:  &amp;lt;TASK&amp;gt;  schedule+0x483/0x1370  schedule_preempt_disabled+0x15/0x30  __mutex_lock_common+0x1fd/0x470  __rtl8152_set_mac_address+0x80/0x1f0  dev_set_mac_address+0x7f/0x150  rtl8152_post_reset+0x72/0x150  usb_reset_device+0x1d0/0x220  rtl8152_resume+0x99/0xc0  usb_resume_interface+0x3e/0xc0  usb_resume_both+0x104/0x150  usb_resume+0x22/0x110 The problem is that rtl8152 resume calls reset under tp-&amp;gt;control mutex while reset basically re-enters rtl8152 and attempts to acquire the same tp-&amp;gt;control lock once again. Reset INACCESSIBLE device outside of tp-&amp;gt;control mutex scope to avoid recursive mutex_lock() deadlock.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23188</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-0421 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0421</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-2026-0421</guid>
    </item>
  </channel>
</rss>
