<?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>Fri, 02 Oct 2026 16:29:11 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-04137</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-04137</link>
      <description>bdu:2024-04137</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-04137</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-26622</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-26622</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-2024-26622</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0242 — De multiples vulnérabilités ont été découvertes dans &lt;span
class="textit"&gt;le noyau Linux de SUSE&lt;/span&gt;. Certaines d'en…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0242</link>
      <description>certfr-2024-avi-0242</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0242</guid>
    </item>
    <item>
      <title>EUVD-2026-312517</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-312517</link>
      <description>EUVD-2026-312517</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-312517</guid>
    </item>
    <item>
      <title>fkie_cve-2024-26622</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-26622</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tomoyo: fix UAF write bug in tomoyo_write_control()&lt;/p&gt;
&lt;p&gt;Since tomoyo_write_control() updates head-&amp;gt;write_buf when write()
of long lines is requested, we need to fetch head-&amp;gt;write_buf after
head-&amp;gt;io_sem is held.  Otherwise, concurrent write() requests can
cause use-after-free-write and double-free problems.&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;tomoyo: fix UAF write bug in tomoyo_write_control()&lt;/p&gt;
&lt;p&gt;Since tomoyo_write_control() updates head-&amp;gt;write_buf when write()
of long lines is requested, we need to fetch head-&amp;gt;write_buf after
head-&amp;gt;io_sem is held.  Otherwise, concurrent write() requests can
cause use-after-free-write and double-free problems.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-26622</guid>
    </item>
    <item>
      <title>GHSA-hmvg-cx6j-hfj7</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-hmvg-cx6j-hfj7</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tomoyo: fix UAF write bug in tomoyo_write_control()&lt;/p&gt;
&lt;p&gt;Since tomoyo_write_control() updates head-&amp;gt;write_buf when write()
of long lines is requested, we need to fetch head-&amp;gt;write_buf after
head-&amp;gt;io_sem is held.  Otherwise, concurrent write() requests can
cause use-after-free-write and double-free problems.&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;tomoyo: fix UAF write bug in tomoyo_write_control()&lt;/p&gt;
&lt;p&gt;Since tomoyo_write_control() updates head-&amp;gt;write_buf when write()
of long lines is requested, we need to fetch head-&amp;gt;write_buf after
head-&amp;gt;io_sem is held.  Otherwise, concurrent write() requests can
cause use-after-free-write and double-free problems.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-hmvg-cx6j-hfj7</guid>
    </item>
    <item>
      <title>gsd-2024-26622</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2024-26622</link>
      <description>gsd-2024-26622</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2024-26622</guid>
    </item>
    <item>
      <title>OESA-2024-1353 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-1353</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
KVM: x86/mmu: Don&amp;amp;apos;t advance iterator after restart due to yielding&#13;
&#13;
After dropping mmu_lock in the TDP MMU, restart the iterator during
tdp_iter_next() and do not advance the iterator.  Advancing the iterator
results in skipping the top-level SPTE and all its children, which is
fatal if any of the skipped SPTEs were not visited before yielding.&#13;
&#13;
When zapping all SPTEs, i.e. when min_level == root_level, restarting the
iter and then invoking tdp_iter_next() is always fatal if the current gfn
has as a valid SPTE, as advancing the iterator results in try_step_side()
skipping the current gfn, which wasn&amp;amp;apos;t visited before yielding.&#13;
&#13;
Sprinkle WARNs on iter-&amp;amp;gt;yielded being true in various helpers that are
often used in conjunction with yielding, and tag the helper with
__must_check to reduce the probabily of improper usage.&#13;
&#13;
Failing to zap a top-level SPTE manifests in one of two ways.  If a valid
SPTE is skipped by both kvm_tdp_mmu_zap_all() and kvm_tdp_mmu_put_root(),
the shadow page will be leaked and KVM will WARN accordingly.&#13;
&#13;
  WARNING: CPU: 1 PID: 3509 at arch/x86/kvm/mmu/tdp_mmu.c:46 [kvm]
  RIP: 0010:kvm_mmu_uninit_tdp_mmu+0x3e/0x50 [kvm]
  Call Trace:
   &amp;amp;lt;TASK&amp;amp;gt;
   kvm_arch_destroy_vm+0x130/0x1b0 [kvm]
   kvm_destroy_vm+0x162/0x2a0 [kvm]
   kvm_vcpu_release+0x34/0x60 [kvm]
   __fput+0x82/0x240
   task_…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
KVM: x86/mmu: Don&amp;amp;apos;t advance iterator after restart due to yielding&#13;
&#13;
After dropping mmu_lock in the TDP MMU, restart the iterator during
tdp_iter_next() and do not advance the iterator.  Advancing the iterator
results in skipping the top-level SPTE and all its children, which is
fatal if any of the skipped SPTEs were not visited before yielding.&#13;
&#13;
When zapping all SPTEs, i.e. when min_level == root_level, restarting the
iter and then invoking tdp_iter_next() is always fatal if the current gfn
has as a valid SPTE, as advancing the iterator results in try_step_side()
skipping the current gfn, which wasn&amp;amp;apos;t visited before yielding.&#13;
&#13;
Sprinkle WARNs on iter-&amp;amp;gt;yielded being true in various helpers that are
often used in conjunction with yielding, and tag the helper with
__must_check to reduce the probabily of improper usage.&#13;
&#13;
Failing to zap a top-level SPTE manifests in one of two ways.  If a valid
SPTE is skipped by both kvm_tdp_mmu_zap_all() and kvm_tdp_mmu_put_root(),
the shadow page will be leaked and KVM will WARN accordingly.&#13;
&#13;
  WARNING: CPU: 1 PID: 3509 at arch/x86/kvm/mmu/tdp_mmu.c:46 [kvm]
  RIP: 0010:kvm_mmu_uninit_tdp_mmu+0x3e/0x50 [kvm]
  Call Trace:
   &amp;amp;lt;TASK&amp;amp;gt;
   kvm_arch_destroy_vm+0x130/0x1b0 [kvm]
   kvm_destroy_vm+0x162/0x2a0 [kvm]
   kvm_vcpu_release+0x34/0x60 [kvm]
   __fput+0x82/0x240
   task_…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-1353</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:0855-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:0855-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-2024:0855-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-26622</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-26622</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 159 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: tomoyo: fix UAF write bug in tomoyo_write_control() Since tomoyo_write_control() updates head-&amp;gt;write_buf when write() of long lines is requested, we need to fetch head-&amp;gt;write_buf after head-&amp;gt;io_sem is held.  Otherwise, concurrent write() requests can cause use-after-free-write and double-free problems.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 159 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: tomoyo: fix UAF write bug in tomoyo_write_control() Since tomoyo_write_control() updates head-&amp;gt;write_buf when write() of long lines is requested, we need to fetch head-&amp;gt;write_buf after head-&amp;gt;io_sem is held.  Otherwise, concurrent write() requests can cause use-after-free-write and double-free problems.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-26622</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-0536 — Linux Kernel: Schwachstelle ermöglicht nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0536</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann eine Schwachstelle im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann eine Schwachstelle im Linux Kernel ausnutzen, um 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-0536</guid>
    </item>
  </channel>
</rss>
