<?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, 03 Oct 2026 08:19:43 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-90046</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-90046</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-2026-90046</guid>
    </item>
    <item>
      <title>EUVD-2026-369534</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-369534</link>
      <description>EUVD-2026-369534</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-369534</guid>
    </item>
    <item>
      <title>fkie_cve-2026-90046</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-90046</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/page_alloc: don&amp;#39;t spin_trylock() in NMI on UP&lt;/p&gt;
&lt;p&gt;Patch series &amp;#34;mm/page_alloc: fixes for free_pages_nolock() on RT/UP&amp;#34;.&lt;/p&gt;
&lt;p&gt;Pre-existing bugs found by Sashiko during review of this other series:
https://lore.kernel.org/all/20260703-alloc-trylock-v5-0-c87b714e19d3@google.com/&lt;/p&gt;
&lt;p&gt;I have not reproduced these bugs, and I suspect there is no real-world
user that is affected by them.&lt;/p&gt;
&lt;p&gt;This patch (of 2):&lt;/p&gt;
&lt;p&gt;As noted in can_spin_trylock(), using this is unsafe in this context. 
commit 620b46ed6ae17 (&amp;#34;mm/page_alloc: return NULL early from
alloc_frozen_pages_nolock() in NMI on UP&amp;#34;) fixed this on the alloc side
but missed the free side.&lt;/p&gt;
&lt;p&gt;Impact: If BPF programs using these features in NMI (probably tracing) are
present on non-SMP builds this might crash the kernel and is probably
exploitable by local attackers for privilege escalation.&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;mm/page_alloc: don&amp;#39;t spin_trylock() in NMI on UP&lt;/p&gt;
&lt;p&gt;Patch series &amp;#34;mm/page_alloc: fixes for free_pages_nolock() on RT/UP&amp;#34;.&lt;/p&gt;
&lt;p&gt;Pre-existing bugs found by Sashiko during review of this other series:
https://lore.kernel.org/all/20260703-alloc-trylock-v5-0-c87b714e19d3@google.com/&lt;/p&gt;
&lt;p&gt;I have not reproduced these bugs, and I suspect there is no real-world
user that is affected by them.&lt;/p&gt;
&lt;p&gt;This patch (of 2):&lt;/p&gt;
&lt;p&gt;As noted in can_spin_trylock(), using this is unsafe in this context. 
commit 620b46ed6ae17 (&amp;#34;mm/page_alloc: return NULL early from
alloc_frozen_pages_nolock() in NMI on UP&amp;#34;) fixed this on the alloc side
but missed the free side.&lt;/p&gt;
&lt;p&gt;Impact: If BPF programs using these features in NMI (probably tracing) are
present on non-SMP builds this might crash the kernel and is probably
exploitable by local attackers for privilege escalation.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-90046</guid>
    </item>
    <item>
      <title>GHSA-h63h-wcx8-jm4r</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-h63h-wcx8-jm4r</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/page_alloc: don&amp;#39;t spin_trylock() in NMI on UP&lt;/p&gt;
&lt;p&gt;Patch series &amp;#34;mm/page_alloc: fixes for free_pages_nolock() on RT/UP&amp;#34;.&lt;/p&gt;
&lt;p&gt;Pre-existing bugs found by Sashiko during review of this other series:
https://lore.kernel.org/all/20260703-alloc-trylock-v5-0-c87b714e19d3@google.com/&lt;/p&gt;
&lt;p&gt;I have not reproduced these bugs, and I suspect there is no real-world
user that is affected by them.&lt;/p&gt;
&lt;p&gt;This patch (of 2):&lt;/p&gt;
&lt;p&gt;As noted in can_spin_trylock(), using this is unsafe in this context. 
commit 620b46ed6ae17 (&amp;#34;mm/page_alloc: return NULL early from
alloc_frozen_pages_nolock() in NMI on UP&amp;#34;) fixed this on the alloc side
but missed the free side.&lt;/p&gt;
&lt;p&gt;Impact: If BPF programs using these features in NMI (probably tracing) are
present on non-SMP builds this might crash the kernel and is probably
exploitable by local attackers for privilege escalation.&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;mm/page_alloc: don&amp;#39;t spin_trylock() in NMI on UP&lt;/p&gt;
&lt;p&gt;Patch series &amp;#34;mm/page_alloc: fixes for free_pages_nolock() on RT/UP&amp;#34;.&lt;/p&gt;
&lt;p&gt;Pre-existing bugs found by Sashiko during review of this other series:
https://lore.kernel.org/all/20260703-alloc-trylock-v5-0-c87b714e19d3@google.com/&lt;/p&gt;
&lt;p&gt;I have not reproduced these bugs, and I suspect there is no real-world
user that is affected by them.&lt;/p&gt;
&lt;p&gt;This patch (of 2):&lt;/p&gt;
&lt;p&gt;As noted in can_spin_trylock(), using this is unsafe in this context. 
commit 620b46ed6ae17 (&amp;#34;mm/page_alloc: return NULL early from
alloc_frozen_pages_nolock() in NMI on UP&amp;#34;) fixed this on the alloc side
but missed the free side.&lt;/p&gt;
&lt;p&gt;Impact: If BPF programs using these features in NMI (probably tracing) are
present on non-SMP builds this might crash the kernel and is probably
exploitable by local attackers for privilege escalation.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-h63h-wcx8-jm4r</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11880-1 — kernel-devel-7.2.7-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:11880-1</link>
      <description>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:11880-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-90046</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-90046</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 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mm/page_alloc: don&amp;#39;t spin_trylock() in NMI on UP Patch series &amp;#34;mm/page_alloc: fixes for free_pages_nolock() on RT/UP&amp;#34;. Pre-existing bugs found by Sashiko during review of this other series: https://lore.kernel.org/all/20260703-alloc-trylock-v5-0-c87b714e19d3@google.com/ I have not reproduced these bugs, and I suspect there is no real-world user that is affected by them. This patch (of 2): As noted in can_spin_trylock(), using this is unsafe in this context. commit 620b46ed6ae17 (&amp;#34;mm/page_alloc: return NULL early from alloc_frozen_pages_nolock() in NMI on UP&amp;#34;) fixed this on the alloc side but missed the free side. Impact: If BPF programs using these features in NMI (probably tracing) are present on non-SMP builds this might crash the kernel and is probably exploitable by local attackers for privilege escalation.&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 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mm/page_alloc: don&amp;#39;t spin_trylock() in NMI on UP Patch series &amp;#34;mm/page_alloc: fixes for free_pages_nolock() on RT/UP&amp;#34;. Pre-existing bugs found by Sashiko during review of this other series: https://lore.kernel.org/all/20260703-alloc-trylock-v5-0-c87b714e19d3@google.com/ I have not reproduced these bugs, and I suspect there is no real-world user that is affected by them. This patch (of 2): As noted in can_spin_trylock(), using this is unsafe in this context. commit 620b46ed6ae17 (&amp;#34;mm/page_alloc: return NULL early from alloc_frozen_pages_nolock() in NMI on UP&amp;#34;) fixed this on the alloc side but missed the free side. Impact: If BPF programs using these features in NMI (probably tracing) are present on non-SMP builds this might crash the kernel and is probably exploitable by local attackers for privilege escalation.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-90046</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3438 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3438</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service zu verursachen oder eine nicht näher spezifizierte Auswirkung zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service zu verursachen oder eine nicht näher spezifizierte Auswirkung zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3438</guid>
    </item>
  </channel>
</rss>
