<?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://db.gcve.eu</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>Thu, 19 Nov 2026 17:27:38 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-40953 — KVM: Fix a data race on last_boosted_vcpu in kvm_vcpu_on_spin()</title>
      <link>https://db.gcve.eu/vuln/cve-2024-40953</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: Fix a data race on last_boosted_vcpu in kvm_vcpu_on_spin()&lt;/p&gt;
&lt;p&gt;Use {READ,WRITE}_ONCE() to access kvm-&amp;gt;last_boosted_vcpu to ensure the
loads and stores are atomic.  In the extremely unlikely scenario the
compiler tears the stores, it&amp;#39;s theoretically possible for KVM to attempt
to get a vCPU using an out-of-bounds index, e.g. if the write is split
into multiple 8-bit stores, and is paired with a 32-bit load on a VM with
257 vCPUs:&lt;/p&gt;
&lt;p&gt;CPU0                              CPU1
  last_boosted_vcpu = 0xff;&lt;/p&gt;
&lt;p&gt;(last_boosted_vcpu = 0x100)
                                    last_boosted_vcpu[15:8] = 0x01;
  i = (last_boosted_vcpu = 0x1ff)
                                    last_boosted_vcpu[7:0] = 0x00;&lt;/p&gt;
&lt;p&gt;vcpu = kvm-&amp;gt;vcpu_array[0x1ff];&lt;/p&gt;
&lt;p&gt;As detected by KCSAN:&lt;/p&gt;
&lt;p&gt;BUG: KCSAN: data-race in kvm_vcpu_on_spin [kvm] / kvm_vcpu_on_spin [kvm]&lt;/p&gt;
&lt;p&gt;write to 0xffffc90025a92344 of 4 bytes by task 4340 on cpu 16:
  kvm_vcpu_on_spin (arch/x86/kvm/../../../virt/kvm/kvm_main.c:4112) kvm
  handle_pause (arch/x86/kvm/vmx/vmx.c:5929) kvm_intel
  vmx_handle_exit (arch/x86/kvm/vmx/vmx.c:?
		 arch/x86/kvm/vmx/vmx.c:6606) kvm_intel
  vcpu_run (arch/x86/kvm/x86.c:11107 arch/x86/kvm/x86.c:11211) kvm
  kvm_arch_vcpu_ioctl_run (arch/x86/kvm/x86.c:?) kvm
  kvm_vcpu_ioctl (arch/x86/kvm/../../../virt/kvm/kvm_main.c:?) kvm
  __se_sys_ioctl (fs/ioctl.c:52 fs/ioctl.c:904 fs/ioctl.c:890)
  __x64_sys_ioctl (fs/ioctl.c…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: Fix a data race on last_boosted_vcpu in kvm_vcpu_on_spin()&lt;/p&gt;
&lt;p&gt;Use {READ,WRITE}_ONCE() to access kvm-&amp;gt;last_boosted_vcpu to ensure the
loads and stores are atomic.  In the extremely unlikely scenario the
compiler tears the stores, it&amp;#39;s theoretically possible for KVM to attempt
to get a vCPU using an out-of-bounds index, e.g. if the write is split
into multiple 8-bit stores, and is paired with a 32-bit load on a VM with
257 vCPUs:&lt;/p&gt;
&lt;p&gt;CPU0                              CPU1
  last_boosted_vcpu = 0xff;&lt;/p&gt;
&lt;p&gt;(last_boosted_vcpu = 0x100)
                                    last_boosted_vcpu[15:8] = 0x01;
  i = (last_boosted_vcpu = 0x1ff)
                                    last_boosted_vcpu[7:0] = 0x00;&lt;/p&gt;
&lt;p&gt;vcpu = kvm-&amp;gt;vcpu_array[0x1ff];&lt;/p&gt;
&lt;p&gt;As detected by KCSAN:&lt;/p&gt;
&lt;p&gt;BUG: KCSAN: data-race in kvm_vcpu_on_spin [kvm] / kvm_vcpu_on_spin [kvm]&lt;/p&gt;
&lt;p&gt;write to 0xffffc90025a92344 of 4 bytes by task 4340 on cpu 16:
  kvm_vcpu_on_spin (arch/x86/kvm/../../../virt/kvm/kvm_main.c:4112) kvm
  handle_pause (arch/x86/kvm/vmx/vmx.c:5929) kvm_intel
  vmx_handle_exit (arch/x86/kvm/vmx/vmx.c:?
		 arch/x86/kvm/vmx/vmx.c:6606) kvm_intel
  vcpu_run (arch/x86/kvm/x86.c:11107 arch/x86/kvm/x86.c:11211) kvm
  kvm_arch_vcpu_ioctl_run (arch/x86/kvm/x86.c:?) kvm
  kvm_vcpu_ioctl (arch/x86/kvm/../../../virt/kvm/kvm_main.c:?) kvm
  __se_sys_ioctl (fs/ioctl.c:52 fs/ioctl.c:904 fs/ioctl.c:890)
  __x64_sys_ioctl (fs/ioctl.c…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2024-40953</guid>
    </item>
    <item>
      <title>USN-6999-1 — linux, linux-aws, linux-gcp, linux-gke, linux-ibm, linux-lowlatency, linux-oem-6.8, linux-oracle vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-6999-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux, Ubuntu:24.04:LTS: linux-aws, Ubuntu:24.04:LTS: linux-gcp, Ubuntu:24.04:LTS: linux-gke, Ubuntu:24.04:LTS: linux-ibm, Ubuntu:24.04:LTS: linux-lowlatency, Ubuntu:24.04:LTS: linux-oem-6.8, Ubuntu:24.04:LTS: linux-oracle&lt;/p&gt;
&lt;p&gt;Chenyuan Yang discovered that the CEC driver driver in the Linux kernel
contained a use-after-free vulnerability. A local attacker could use this
to cause a denial of service (system crash) or possibly execute arbitrary
code. (CVE-2024-23848)&lt;/p&gt;
&lt;p&gt;It was discovered that the JFS file system contained an out-of-bounds read
vulnerability when printing xattr debug information. A local attacker could
use this to cause a denial of service (system crash). (CVE-2024-40902)&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - MIPS architecture;
  - PA-RISC architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - x86 architecture;
  - Block layer subsystem;
  - ACPI drivers;
  - Drivers core;
  - Null block device driver;
  - Character device driver;
  - TPM device driver;
  - Clock framework and drivers;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - Buffer Sharing and Synchronization framework;
  - DMA engine subsystem;
  - EFI core;
  - FPGA Framework;
  - GPU drivers;
  - Greybus drivers;
  - HID subsystem;
  - HW tracing;
  - I2C subsystem;
  - IIO subsystem;
  - InfiniBand drivers;
  - Input Device (Mouse) drivers;
  - Mailbox framework;
  - Media drivers;
  - Microchip PCI driver;
  - VMware VMCI Driver;
  - Network drivers;
  - PCI subsystem;
  -…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux, Ubuntu:24.04:LTS: linux-aws, Ubuntu:24.04:LTS: linux-gcp, Ubuntu:24.04:LTS: linux-gke, Ubuntu:24.04:LTS: linux-ibm, Ubuntu:24.04:LTS: linux-lowlatency, Ubuntu:24.04:LTS: linux-oem-6.8, Ubuntu:24.04:LTS: linux-oracle&lt;/p&gt;
&lt;p&gt;Chenyuan Yang discovered that the CEC driver driver in the Linux kernel
contained a use-after-free vulnerability. A local attacker could use this
to cause a denial of service (system crash) or possibly execute arbitrary
code. (CVE-2024-23848)&lt;/p&gt;
&lt;p&gt;It was discovered that the JFS file system contained an out-of-bounds read
vulnerability when printing xattr debug information. A local attacker could
use this to cause a denial of service (system crash). (CVE-2024-40902)&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - MIPS architecture;
  - PA-RISC architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - x86 architecture;
  - Block layer subsystem;
  - ACPI drivers;
  - Drivers core;
  - Null block device driver;
  - Character device driver;
  - TPM device driver;
  - Clock framework and drivers;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - Buffer Sharing and Synchronization framework;
  - DMA engine subsystem;
  - EFI core;
  - FPGA Framework;
  - GPU drivers;
  - Greybus drivers;
  - HID subsystem;
  - HW tracing;
  - I2C subsystem;
  - IIO subsystem;
  - InfiniBand drivers;
  - Input Device (Mouse) drivers;
  - Mailbox framework;
  - Media drivers;
  - Microchip PCI driver;
  - VMware VMCI Driver;
  - Network drivers;
  - PCI subsystem;
  -…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-6999-1</guid>
    </item>
  </channel>
</rss>
