<?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>Sat, 10 Oct 2026 16:29:29 +0000</lastBuildDate>
    <item>
      <title>Withdrawn: BELL-CVE-2026-53326 — CVE-2026-53326 does not affect BellSoft software</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-53326</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-53326</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1162 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1162</link>
      <description>certfr-2026-avi-1162</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1162</guid>
    </item>
    <item>
      <title>EUVD-2026-332517</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-332517</link>
      <description>EUVD-2026-332517</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-332517</guid>
    </item>
    <item>
      <title>fkie_cve-2026-53326</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-53326</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;debugobjects: Don&amp;#39;t call fill_pool() in early boot hardirq context&lt;/p&gt;
&lt;p&gt;When booting a debug PREEMPT_RT kernel on an ARM64 system, a &amp;#34;inconsistent
{HARDIRQ-ON-W} -&amp;gt; {IN-HARDIRQ-W} usage&amp;#34; lockdep warning message was
reported to the console.&lt;/p&gt;
&lt;p&gt;During early boot, interrupts are enabled before the scheduler is
enabled. In this window (before SYSTEM_SCHEDULING is set) interrupts can
fire and in the hard interrupt context handler attempt to fill the pool&lt;/p&gt;
&lt;p&gt;This can lead to a deadlock when the interrupt occurred when the interrupt
hits a region which holds a lock that is required to be taken in the
allocation path.&lt;/p&gt;
&lt;p&gt;Add a new can_fill_pool() helper and reorder the exception rule and forbid
this scenario by excluding allocations from hard interrupt context.&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;debugobjects: Don&amp;#39;t call fill_pool() in early boot hardirq context&lt;/p&gt;
&lt;p&gt;When booting a debug PREEMPT_RT kernel on an ARM64 system, a &amp;#34;inconsistent
{HARDIRQ-ON-W} -&amp;gt; {IN-HARDIRQ-W} usage&amp;#34; lockdep warning message was
reported to the console.&lt;/p&gt;
&lt;p&gt;During early boot, interrupts are enabled before the scheduler is
enabled. In this window (before SYSTEM_SCHEDULING is set) interrupts can
fire and in the hard interrupt context handler attempt to fill the pool&lt;/p&gt;
&lt;p&gt;This can lead to a deadlock when the interrupt occurred when the interrupt
hits a region which holds a lock that is required to be taken in the
allocation path.&lt;/p&gt;
&lt;p&gt;Add a new can_fill_pool() helper and reorder the exception rule and forbid
this scenario by excluding allocations from hard interrupt context.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-53326</guid>
    </item>
    <item>
      <title>GHSA-r6vx-43g9-hvqx</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-r6vx-43g9-hvqx</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;debugobjects: Don&amp;#39;t call fill_pool() in early boot hardirq context&lt;/p&gt;
&lt;p&gt;When booting a debug PREEMPT_RT kernel on an ARM64 system, a &amp;#34;inconsistent
{HARDIRQ-ON-W} -&amp;gt; {IN-HARDIRQ-W} usage&amp;#34; lockdep warning message was
reported to the console.&lt;/p&gt;
&lt;p&gt;During early boot, interrupts are enabled before the scheduler is
enabled. In this window (before SYSTEM_SCHEDULING is set) interrupts can
fire and in the hard interrupt context handler attempt to fill the pool&lt;/p&gt;
&lt;p&gt;This can lead to a deadlock when the interrupt occurred when the interrupt
hits a region which holds a lock that is required to be taken in the
allocation path.&lt;/p&gt;
&lt;p&gt;Add a new can_fill_pool() helper and reorder the exception rule and forbid
this scenario by excluding allocations from hard interrupt context.&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;debugobjects: Don&amp;#39;t call fill_pool() in early boot hardirq context&lt;/p&gt;
&lt;p&gt;When booting a debug PREEMPT_RT kernel on an ARM64 system, a &amp;#34;inconsistent
{HARDIRQ-ON-W} -&amp;gt; {IN-HARDIRQ-W} usage&amp;#34; lockdep warning message was
reported to the console.&lt;/p&gt;
&lt;p&gt;During early boot, interrupts are enabled before the scheduler is
enabled. In this window (before SYSTEM_SCHEDULING is set) interrupts can
fire and in the hard interrupt context handler attempt to fill the pool&lt;/p&gt;
&lt;p&gt;This can lead to a deadlock when the interrupt occurred when the interrupt
hits a region which holds a lock that is required to be taken in the
allocation path.&lt;/p&gt;
&lt;p&gt;Add a new can_fill_pool() helper and reorder the exception rule and forbid
this scenario by excluding allocations from hard interrupt context.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-r6vx-43g9-hvqx</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-53326</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-53326</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 110 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: debugobjects: Don&amp;#39;t call fill_pool() in early boot hardirq context When booting a debug PREEMPT_RT kernel on an ARM64 system, a &amp;#34;inconsistent {HARDIRQ-ON-W} -&amp;gt; {IN-HARDIRQ-W} usage&amp;#34; lockdep warning message was reported to the console. During early boot, interrupts are enabled before the scheduler is enabled. In this window (before SYSTEM_SCHEDULING is set) interrupts can fire and in the hard interrupt context handler attempt to fill the pool This can lead to a deadlock when the interrupt occurred when the interrupt hits a region which holds a lock that is required to be taken in the allocation path. Add a new can_fill_pool() helper and reorder the exception rule and forbid this scenario by excluding allocations from hard interrupt context.&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 110 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: debugobjects: Don&amp;#39;t call fill_pool() in early boot hardirq context When booting a debug PREEMPT_RT kernel on an ARM64 system, a &amp;#34;inconsistent {HARDIRQ-ON-W} -&amp;gt; {IN-HARDIRQ-W} usage&amp;#34; lockdep warning message was reported to the console. During early boot, interrupts are enabled before the scheduler is enabled. In this window (before SYSTEM_SCHEDULING is set) interrupts can fire and in the hard interrupt context handler attempt to fill the pool This can lead to a deadlock when the interrupt occurred when the interrupt hits a region which holds a lock that is required to be taken in the allocation path. Add a new can_fill_pool() helper and reorder the exception rule and forbid this scenario by excluding allocations from hard interrupt context.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-53326</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2175 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2175</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise das Auslösen eines Denial-of-Service-Zustands, die Umgehung von Sicherheitsmaßnahmen oder das Verursachen von Speicherbeschädigungen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise das Auslösen eines Denial-of-Service-Zustands, die Umgehung von Sicherheitsmaßnahmen oder das Verursachen von Speicherbeschädigungen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2175</guid>
    </item>
  </channel>
</rss>
