<?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>Wed, 14 Oct 2026 19:07:53 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-21839 — KVM: x86: Load DR6 with guest value only before entering .vcpu_run() loop</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-21839</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: x86: Load DR6 with guest value only before entering .vcpu_run() loop&lt;/p&gt;
&lt;p&gt;Move the conditional loading of hardware DR6 with the guest&amp;#39;s DR6 value
out of the core .vcpu_run() loop to fix a bug where KVM can load hardware
with a stale vcpu-&amp;gt;arch.dr6.&lt;/p&gt;
&lt;p&gt;When the guest accesses a DR and host userspace isn&amp;#39;t debugging the guest,
KVM disables DR interception and loads the guest&amp;#39;s values into hardware on
VM-Enter and saves them on VM-Exit.  This allows the guest to access DRs
at will, e.g. so that a sequence of DR accesses to configure a breakpoint
only generates one VM-Exit.&lt;/p&gt;
&lt;p&gt;For DR0-DR3, the logic/behavior is identical between VMX and SVM, and also
identical between KVM_DEBUGREG_BP_ENABLED (userspace debugging the guest)
and KVM_DEBUGREG_WONT_EXIT (guest using DRs), and so KVM handles loading
DR0-DR3 in common code, _outside_ of the core kvm_x86_ops.vcpu_run() loop.&lt;/p&gt;
&lt;p&gt;But for DR6, the guest&amp;#39;s value doesn&amp;#39;t need to be loaded into hardware for
KVM_DEBUGREG_BP_ENABLED, and SVM provides a dedicated VMCB field whereas
VMX requires software to manually load the guest value, and so loading the
guest&amp;#39;s value into DR6 is handled by {svm,vmx}_vcpu_run(), i.e. is done
_inside_ the core run loop.&lt;/p&gt;
&lt;p&gt;Unfortunately, saving the guest values on VM-Exit is initiated by common
x86, again outside of the core run loop.  If the guest modifies DR6 (in
hardware, when DR interception is disabled), and then the next VM-Exit is
a fastpath V…&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: x86: Load DR6 with guest value only before entering .vcpu_run() loop&lt;/p&gt;
&lt;p&gt;Move the conditional loading of hardware DR6 with the guest&amp;#39;s DR6 value
out of the core .vcpu_run() loop to fix a bug where KVM can load hardware
with a stale vcpu-&amp;gt;arch.dr6.&lt;/p&gt;
&lt;p&gt;When the guest accesses a DR and host userspace isn&amp;#39;t debugging the guest,
KVM disables DR interception and loads the guest&amp;#39;s values into hardware on
VM-Enter and saves them on VM-Exit.  This allows the guest to access DRs
at will, e.g. so that a sequence of DR accesses to configure a breakpoint
only generates one VM-Exit.&lt;/p&gt;
&lt;p&gt;For DR0-DR3, the logic/behavior is identical between VMX and SVM, and also
identical between KVM_DEBUGREG_BP_ENABLED (userspace debugging the guest)
and KVM_DEBUGREG_WONT_EXIT (guest using DRs), and so KVM handles loading
DR0-DR3 in common code, _outside_ of the core kvm_x86_ops.vcpu_run() loop.&lt;/p&gt;
&lt;p&gt;But for DR6, the guest&amp;#39;s value doesn&amp;#39;t need to be loaded into hardware for
KVM_DEBUGREG_BP_ENABLED, and SVM provides a dedicated VMCB field whereas
VMX requires software to manually load the guest value, and so loading the
guest&amp;#39;s value into DR6 is handled by {svm,vmx}_vcpu_run(), i.e. is done
_inside_ the core run loop.&lt;/p&gt;
&lt;p&gt;Unfortunately, saving the guest values on VM-Exit is initiated by common
x86, again outside of the core run loop.  If the guest modifies DR6 (in
hardware, when DR interception is disabled), and then the next VM-Exit is
a fastpath V…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-21839</guid>
    </item>
    <item>
      <title>USN-7521-1 — linux, linux-azure, linux-azure-6.11, linux-gcp, linux-gcp-6.11, linux-hwe-6.11, linux-oem-6.11, linux-raspi, linux-rea…</title>
      <link>https://cve.radiocsirt.org/vuln/usn-7521-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-azure-6.11, Ubuntu:24.04:LTS: linux-gcp-6.11, Ubuntu:24.04:LTS: linux-hwe-6.11, Ubuntu:24.04:LTS: linux-oem-6.11&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;
  - PowerPC architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Serial ATA and Parallel ATA drivers;
  - Drivers core;
  - Network block device driver;
  - Bluetooth drivers;
  - Character device driver;
  - TPM device driver;
  - Clock framework and drivers;
  - Hardware crypto device drivers;
  - FireWire subsystem;
  - EFI core;
  - Qualcomm firmware drivers;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - I2C subsystem;
  - I3C subsystem;
  - InfiniBand drivers;
  - Input Device (Mouse) drivers;
  - IOMMU subsystem;
  - Multiple devices driver;
  - Media drivers;
  - NVIDIA Tegra memory controller driver;
  - Fastrpc Driver;
  - Network drivers;
  - Operating Performance Points (OPP) driver;
  - PCI subsystem;
  - x86 platform drivers;
  - PPS (Pulse Per Second) driver;
  - PTP clock framework;
  - Remote Processor subsystem;
  - Real Time Clock drivers;
  - S/390 drivers;
  - SCSI subsystem;
  - QCOM SoC drivers;
  - SPI subsystem;
  - Media staging drivers;
  - Trusted Execution Environment drivers;
  - TTY drivers;
  - UFS subsystem;
  - USB Device Class drivers;
  - USB core drivers;
  - USB Gadget drivers;
  - USB Host Controller drivers;
  - Framebuffer layer;
  - File systems infrastructure;
  - BTRFS file system;
  - Ceph distributed fi…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-azure-6.11, Ubuntu:24.04:LTS: linux-gcp-6.11, Ubuntu:24.04:LTS: linux-hwe-6.11, Ubuntu:24.04:LTS: linux-oem-6.11&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;
  - PowerPC architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Serial ATA and Parallel ATA drivers;
  - Drivers core;
  - Network block device driver;
  - Bluetooth drivers;
  - Character device driver;
  - TPM device driver;
  - Clock framework and drivers;
  - Hardware crypto device drivers;
  - FireWire subsystem;
  - EFI core;
  - Qualcomm firmware drivers;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - I2C subsystem;
  - I3C subsystem;
  - InfiniBand drivers;
  - Input Device (Mouse) drivers;
  - IOMMU subsystem;
  - Multiple devices driver;
  - Media drivers;
  - NVIDIA Tegra memory controller driver;
  - Fastrpc Driver;
  - Network drivers;
  - Operating Performance Points (OPP) driver;
  - PCI subsystem;
  - x86 platform drivers;
  - PPS (Pulse Per Second) driver;
  - PTP clock framework;
  - Remote Processor subsystem;
  - Real Time Clock drivers;
  - S/390 drivers;
  - SCSI subsystem;
  - QCOM SoC drivers;
  - SPI subsystem;
  - Media staging drivers;
  - Trusted Execution Environment drivers;
  - TTY drivers;
  - UFS subsystem;
  - USB Device Class drivers;
  - USB core drivers;
  - USB Gadget drivers;
  - USB Host Controller drivers;
  - Framebuffer layer;
  - File systems infrastructure;
  - BTRFS file system;
  - Ceph distributed fi…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-7521-1</guid>
    </item>
  </channel>
</rss>
