<?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 07:06:53 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-03685</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-03685</link>
      <description>bdu:2026-03685</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-03685</guid>
    </item>
    <item>
      <title>certfr-2025-avi-1057 — De multiples vulnérabilités ont été découvertes dans les produits VMware. Elles permettent à un attaquant de provoquer…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-1057</link>
      <description>certfr-2025-avi-1057</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-1057</guid>
    </item>
    <item>
      <title>EUVD-2026-344757</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-344757</link>
      <description>EUVD-2026-344757</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-344757</guid>
    </item>
    <item>
      <title>fkie_cve-2022-49557</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-49557</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;x86/fpu: KVM: Set the base guest FPU uABI size to sizeof(struct kvm_xsave)&lt;/p&gt;
&lt;p&gt;Set the starting uABI size of KVM&amp;#39;s guest FPU to &amp;#39;struct kvm_xsave&amp;#39;,
i.e. to KVM&amp;#39;s historical uABI size.  When saving FPU state for usersapce,
KVM (well, now the FPU) sets the FP+SSE bits in the XSAVE header even if
the host doesn&amp;#39;t support XSAVE.  Setting the XSAVE header allows the VM
to be migrated to a host that does support XSAVE without the new host
having to handle FPU state that may or may not be compatible with XSAVE.&lt;/p&gt;
&lt;p&gt;Setting the uABI size to the host&amp;#39;s default size results in out-of-bounds
writes (setting the FP+SSE bits) and data corruption (that is thankfully
caught by KASAN) when running on hosts without XSAVE, e.g. on Core2 CPUs.&lt;/p&gt;
&lt;p&gt;WARN if the default size is larger than KVM&amp;#39;s historical uABI size; all
features that can push the FPU size beyond the historical size must be
opt-in.&lt;/p&gt;
&lt;p&gt;==================================================================
  BUG: KASAN: slab-out-of-bounds in fpu_copy_uabi_to_guest_fpstate+0x86/0x130
  Read of size 8 at addr ffff888011e33a00 by task qemu-build/681
  CPU: 1 PID: 681 Comm: qemu-build Not tainted 5.18.0-rc5-KASAN-amd64 #1
  Hardware name:  /DG35EC, BIOS ECG3510M.86A.0118.2010.0113.1426 01/13/2010
  Call Trace:
   &amp;lt;TASK&amp;gt;
   dump_stack_lvl+0x34/0x45
   print_report.cold+0x45/0x575
   kasan_report+0x9b/0xd0
   fpu_copy_uabi_to_guest_fpstate+0x86/0x130
   kvm_arch_vcpu_ioctl+0x72a/0x1…&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;x86/fpu: KVM: Set the base guest FPU uABI size to sizeof(struct kvm_xsave)&lt;/p&gt;
&lt;p&gt;Set the starting uABI size of KVM&amp;#39;s guest FPU to &amp;#39;struct kvm_xsave&amp;#39;,
i.e. to KVM&amp;#39;s historical uABI size.  When saving FPU state for usersapce,
KVM (well, now the FPU) sets the FP+SSE bits in the XSAVE header even if
the host doesn&amp;#39;t support XSAVE.  Setting the XSAVE header allows the VM
to be migrated to a host that does support XSAVE without the new host
having to handle FPU state that may or may not be compatible with XSAVE.&lt;/p&gt;
&lt;p&gt;Setting the uABI size to the host&amp;#39;s default size results in out-of-bounds
writes (setting the FP+SSE bits) and data corruption (that is thankfully
caught by KASAN) when running on hosts without XSAVE, e.g. on Core2 CPUs.&lt;/p&gt;
&lt;p&gt;WARN if the default size is larger than KVM&amp;#39;s historical uABI size; all
features that can push the FPU size beyond the historical size must be
opt-in.&lt;/p&gt;
&lt;p&gt;==================================================================
  BUG: KASAN: slab-out-of-bounds in fpu_copy_uabi_to_guest_fpstate+0x86/0x130
  Read of size 8 at addr ffff888011e33a00 by task qemu-build/681
  CPU: 1 PID: 681 Comm: qemu-build Not tainted 5.18.0-rc5-KASAN-amd64 #1
  Hardware name:  /DG35EC, BIOS ECG3510M.86A.0118.2010.0113.1426 01/13/2010
  Call Trace:
   &amp;lt;TASK&amp;gt;
   dump_stack_lvl+0x34/0x45
   print_report.cold+0x45/0x575
   kasan_report+0x9b/0xd0
   fpu_copy_uabi_to_guest_fpstate+0x86/0x130
   kvm_arch_vcpu_ioctl+0x72a/0x1…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-49557</guid>
    </item>
    <item>
      <title>GHSA-wj9j-fjjc-mfr6</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-wj9j-fjjc-mfr6</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;x86/fpu: KVM: Set the base guest FPU uABI size to sizeof(struct kvm_xsave)&lt;/p&gt;
&lt;p&gt;Set the starting uABI size of KVM&amp;#39;s guest FPU to &amp;#39;struct kvm_xsave&amp;#39;,
i.e. to KVM&amp;#39;s historical uABI size.  When saving FPU state for usersapce,
KVM (well, now the FPU) sets the FP+SSE bits in the XSAVE header even if
the host doesn&amp;#39;t support XSAVE.  Setting the XSAVE header allows the VM
to be migrated to a host that does support XSAVE without the new host
having to handle FPU state that may or may not be compatible with XSAVE.&lt;/p&gt;
&lt;p&gt;Setting the uABI size to the host&amp;#39;s default size results in out-of-bounds
writes (setting the FP+SSE bits) and data corruption (that is thankfully
caught by KASAN) when running on hosts without XSAVE, e.g. on Core2 CPUs.&lt;/p&gt;
&lt;p&gt;WARN if the default size is larger than KVM&amp;#39;s historical uABI size; all
features that can push the FPU size beyond the historical size must be
opt-in.&lt;/p&gt;
&lt;p&gt;==================================================================
  BUG: KASAN: slab-out-of-bounds in fpu_copy_uabi_to_guest_fpstate+0x86/0x130
  Read of size 8 at addr ffff888011e33a00 by task qemu-build/681
  CPU: 1 PID: 681 Comm: qemu-build Not tainted 5.18.0-rc5-KASAN-amd64 #1
  Hardware name:  /DG35EC, BIOS ECG3510M.86A.0118.2010.0113.1426 01/13/2010
  Call Trace:
   &amp;lt;TASK&amp;gt;
   dump_stack_lvl+0x34/0x45
   print_report.cold+0x45/0x575
   kasan_report+0x9b/0xd0
   fpu_copy_uabi_to_guest_fpstate+0x86/0x130
   kvm_arch_vcpu_ioctl+0x72a/0x1…&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;x86/fpu: KVM: Set the base guest FPU uABI size to sizeof(struct kvm_xsave)&lt;/p&gt;
&lt;p&gt;Set the starting uABI size of KVM&amp;#39;s guest FPU to &amp;#39;struct kvm_xsave&amp;#39;,
i.e. to KVM&amp;#39;s historical uABI size.  When saving FPU state for usersapce,
KVM (well, now the FPU) sets the FP+SSE bits in the XSAVE header even if
the host doesn&amp;#39;t support XSAVE.  Setting the XSAVE header allows the VM
to be migrated to a host that does support XSAVE without the new host
having to handle FPU state that may or may not be compatible with XSAVE.&lt;/p&gt;
&lt;p&gt;Setting the uABI size to the host&amp;#39;s default size results in out-of-bounds
writes (setting the FP+SSE bits) and data corruption (that is thankfully
caught by KASAN) when running on hosts without XSAVE, e.g. on Core2 CPUs.&lt;/p&gt;
&lt;p&gt;WARN if the default size is larger than KVM&amp;#39;s historical uABI size; all
features that can push the FPU size beyond the historical size must be
opt-in.&lt;/p&gt;
&lt;p&gt;==================================================================
  BUG: KASAN: slab-out-of-bounds in fpu_copy_uabi_to_guest_fpstate+0x86/0x130
  Read of size 8 at addr ffff888011e33a00 by task qemu-build/681
  CPU: 1 PID: 681 Comm: qemu-build Not tainted 5.18.0-rc5-KASAN-amd64 #1
  Hardware name:  /DG35EC, BIOS ECG3510M.86A.0118.2010.0113.1426 01/13/2010
  Call Trace:
   &amp;lt;TASK&amp;gt;
   dump_stack_lvl+0x34/0x45
   print_report.cold+0x45/0x575
   kasan_report+0x9b/0xd0
   fpu_copy_uabi_to_guest_fpstate+0x86/0x130
   kvm_arch_vcpu_ioctl+0x72a/0x1…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-wj9j-fjjc-mfr6</guid>
    </item>
    <item>
      <title>RHSA-2022:6460 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2022:6460</link>
      <description>&lt;p&gt;hw: cpu: incomplete clean-up of multi-core shared buffers (aka SBDR) hw: cpu: incomplete clean-up of microarchitectural fill buffers (aka SBDS) hw: cpu: incomplete clean-up in specific special register write operations (aka DRPW) kernel: KVM: x86/mmu: make apf token non-zero to fix bug kernel: x86/fpu: KVM: Set the base guest FPU uABI size to sizeof(struct kvm_xsave) kernel: ice: Fix memory corruption in VF driver&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;hw: cpu: incomplete clean-up of multi-core shared buffers (aka SBDR) hw: cpu: incomplete clean-up of microarchitectural fill buffers (aka SBDS) hw: cpu: incomplete clean-up in specific special register write operations (aka DRPW) kernel: KVM: x86/mmu: make apf token non-zero to fix bug kernel: x86/fpu: KVM: Set the base guest FPU uABI size to sizeof(struct kvm_xsave) kernel: ice: Fix memory corruption in VF driver&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2022:6460</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-49557</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49557</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 69 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: x86/fpu: KVM: Set the base guest FPU uABI size to sizeof(struct kvm_xsave) Set the starting uABI size of KVM&amp;#39;s guest FPU to &amp;#39;struct kvm_xsave&amp;#39;, i.e. to KVM&amp;#39;s historical uABI size.  When saving FPU state for usersapce, KVM (well, now the FPU) sets the FP+SSE bits in the XSAVE header even if the host doesn&amp;#39;t support XSAVE.  Setting the XSAVE header allows the VM to be migrated to a host that does support XSAVE without the new host having to handle FPU state that may or may not be compatible with XSAVE. Setting the uABI size to the host&amp;#39;s default size results in out-of-bounds writes (setting the FP+SSE bits) and data corruption (that is thankfully caught by KASAN) when running on hosts without XSAVE, e.g. on Core2 CPUs. WARN if the default size is larger than KVM&amp;#39;s historical uABI size; all features that can push the FPU size beyond the historical size must be opt-in.   ==================================================================   BUG: KASAN: slab-out-of-bounds in fpu_copy_uabi_to_guest_fpstate+0x86/0x130   Read of size 8 at addr ffff888011e33a00 by task qemu-build/681   CPU: 1 PID: 681 Comm: qemu-build Not tainted 5.18.0-rc5-KASAN-amd64 #1   Hardware name:  /DG35EC, BIOS ECG3510M.86A.0118.2010.0113.1426 01/13/2010   Call Trace:    &amp;lt;TASK&amp;gt;    dump_stack_lvl+0x34/0x45    print_report.cold+0x45/0x575    kasan_report+0x9b/0xd0    fpu_copy_uabi_to_guest_fpstate+0x86/0x130    kvm_arch_vcpu_ioctl+0x72a/0x1c50 […&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 69 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: x86/fpu: KVM: Set the base guest FPU uABI size to sizeof(struct kvm_xsave) Set the starting uABI size of KVM&amp;#39;s guest FPU to &amp;#39;struct kvm_xsave&amp;#39;, i.e. to KVM&amp;#39;s historical uABI size.  When saving FPU state for usersapce, KVM (well, now the FPU) sets the FP+SSE bits in the XSAVE header even if the host doesn&amp;#39;t support XSAVE.  Setting the XSAVE header allows the VM to be migrated to a host that does support XSAVE without the new host having to handle FPU state that may or may not be compatible with XSAVE. Setting the uABI size to the host&amp;#39;s default size results in out-of-bounds writes (setting the FP+SSE bits) and data corruption (that is thankfully caught by KASAN) when running on hosts without XSAVE, e.g. on Core2 CPUs. WARN if the default size is larger than KVM&amp;#39;s historical uABI size; all features that can push the FPU size beyond the historical size must be opt-in.   ==================================================================   BUG: KASAN: slab-out-of-bounds in fpu_copy_uabi_to_guest_fpstate+0x86/0x130   Read of size 8 at addr ffff888011e33a00 by task qemu-build/681   CPU: 1 PID: 681 Comm: qemu-build Not tainted 5.18.0-rc5-KASAN-amd64 #1   Hardware name:  /DG35EC, BIOS ECG3510M.86A.0118.2010.0113.1426 01/13/2010   Call Trace:    &amp;lt;TASK&amp;gt;    dump_stack_lvl+0x34/0x45    print_report.cold+0x45/0x575    kasan_report+0x9b/0xd0    fpu_copy_uabi_to_guest_fpstate+0x86/0x130    kvm_arch_vcpu_ioctl+0x72a/0x1c50 […&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49557</guid>
    </item>
  </channel>
</rss>
