<?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>Mon, 05 Oct 2026 08:09:16 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-04143</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-04143</link>
      <description>bdu:2024-04143</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-04143</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-26617</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-26617</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-2024-26617</guid>
    </item>
    <item>
      <title>EUVD-2026-345464</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-345464</link>
      <description>EUVD-2026-345464</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-345464</guid>
    </item>
    <item>
      <title>fkie_cve-2024-26617</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-26617</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fs/proc/task_mmu: move mmu notification mechanism inside mm lock&lt;/p&gt;
&lt;p&gt;Move mmu notification mechanism inside mm lock to prevent race condition
in other components which depend on it.  The notifier will invalidate
memory range.  Depending upon the number of iterations, different memory
ranges would be invalidated.&lt;/p&gt;
&lt;p&gt;The following warning would be removed by this patch:
WARNING: CPU: 0 PID: 5067 at arch/x86/kvm/../../../virt/kvm/kvm_main.c:734 kvm_mmu_notifier_change_pte+0x860/0x960 arch/x86/kvm/../../../virt/kvm/kvm_main.c:734&lt;/p&gt;
&lt;p&gt;There is no behavioural and performance change with this patch when
there is no component registered with the mmu notifier.&lt;/p&gt;
&lt;p&gt;[akpm@linux-foundation.org: narrow the scope of `range&amp;#39;, per Sean]&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;fs/proc/task_mmu: move mmu notification mechanism inside mm lock&lt;/p&gt;
&lt;p&gt;Move mmu notification mechanism inside mm lock to prevent race condition
in other components which depend on it.  The notifier will invalidate
memory range.  Depending upon the number of iterations, different memory
ranges would be invalidated.&lt;/p&gt;
&lt;p&gt;The following warning would be removed by this patch:
WARNING: CPU: 0 PID: 5067 at arch/x86/kvm/../../../virt/kvm/kvm_main.c:734 kvm_mmu_notifier_change_pte+0x860/0x960 arch/x86/kvm/../../../virt/kvm/kvm_main.c:734&lt;/p&gt;
&lt;p&gt;There is no behavioural and performance change with this patch when
there is no component registered with the mmu notifier.&lt;/p&gt;
&lt;p&gt;[akpm@linux-foundation.org: narrow the scope of `range&amp;#39;, per Sean]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-26617</guid>
    </item>
    <item>
      <title>GHSA-5gxq-j292-75cc</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5gxq-j292-75cc</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fs/proc/task_mmu: move mmu notification mechanism inside mm lock&lt;/p&gt;
&lt;p&gt;Move mmu notification mechanism inside mm lock to prevent race condition
in other components which depend on it.  The notifier will invalidate
memory range.  Depending upon the number of iterations, different memory
ranges would be invalidated.&lt;/p&gt;
&lt;p&gt;The following warning would be removed by this patch:
WARNING: CPU: 0 PID: 5067 at arch/x86/kvm/../../../virt/kvm/kvm_main.c:734 kvm_mmu_notifier_change_pte+0x860/0x960 arch/x86/kvm/../../../virt/kvm/kvm_main.c:734&lt;/p&gt;
&lt;p&gt;There is no behavioural and performance change with this patch when
there is no component registered with the mmu notifier.&lt;/p&gt;
&lt;p&gt;[akpm@linux-foundation.org: narrow the scope of `range&amp;#39;, per Sean]&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;fs/proc/task_mmu: move mmu notification mechanism inside mm lock&lt;/p&gt;
&lt;p&gt;Move mmu notification mechanism inside mm lock to prevent race condition
in other components which depend on it.  The notifier will invalidate
memory range.  Depending upon the number of iterations, different memory
ranges would be invalidated.&lt;/p&gt;
&lt;p&gt;The following warning would be removed by this patch:
WARNING: CPU: 0 PID: 5067 at arch/x86/kvm/../../../virt/kvm/kvm_main.c:734 kvm_mmu_notifier_change_pte+0x860/0x960 arch/x86/kvm/../../../virt/kvm/kvm_main.c:734&lt;/p&gt;
&lt;p&gt;There is no behavioural and performance change with this patch when
there is no component registered with the mmu notifier.&lt;/p&gt;
&lt;p&gt;[akpm@linux-foundation.org: narrow the scope of `range&amp;#39;, per Sean]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5gxq-j292-75cc</guid>
    </item>
    <item>
      <title>gsd-2024-26617</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2024-26617</link>
      <description>gsd-2024-26617</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2024-26617</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-26617</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-26617</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 56 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: fs/proc/task_mmu: move mmu notification mechanism inside mm lock Move mmu notification mechanism inside mm lock to prevent race condition in other components which depend on it.  The notifier will invalidate memory range.  Depending upon the number of iterations, different memory ranges would be invalidated. The following warning would be removed by this patch: WARNING: CPU: 0 PID: 5067 at arch/x86/kvm/../../../virt/kvm/kvm_main.c:734 kvm_mmu_notifier_change_pte+0x860/0x960 arch/x86/kvm/../../../virt/kvm/kvm_main.c:734 There is no behavioural and performance change with this patch when there is no component registered with the mmu notifier. [akpm@linux-foundation.org: narrow the scope of `range&amp;#39;, per Sean]&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 56 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: fs/proc/task_mmu: move mmu notification mechanism inside mm lock Move mmu notification mechanism inside mm lock to prevent race condition in other components which depend on it.  The notifier will invalidate memory range.  Depending upon the number of iterations, different memory ranges would be invalidated. The following warning would be removed by this patch: WARNING: CPU: 0 PID: 5067 at arch/x86/kvm/../../../virt/kvm/kvm_main.c:734 kvm_mmu_notifier_change_pte+0x860/0x960 arch/x86/kvm/../../../virt/kvm/kvm_main.c:734 There is no behavioural and performance change with this patch when there is no component registered with the mmu notifier. [akpm@linux-foundation.org: narrow the scope of `range&amp;#39;, per Sean]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-26617</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-0527 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0527</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand zu verursachen und einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand zu verursachen und einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0527</guid>
    </item>
  </channel>
</rss>
