<?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>Tue, 03 Nov 2026 07:22:07 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-98714</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-98714</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: SVM: Update control fields on #VMEXIT if and only if VMRUN succeeded&lt;/p&gt;
&lt;p&gt;Leave control.erap_ctl and control.clean as-is in the VMCS if VMRUN fails,
because as per AMD:&lt;/p&gt;
&lt;p&gt;there&amp;#39;s no explicit architectural guarantee about the behavior in the
  presence of VMRUN failures. So the best thing to do would be to assume
  that if VMRUN fails, the actions requested in the control fields may not
  have been performed.&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;KVM: SVM: Update control fields on #VMEXIT if and only if VMRUN succeeded&lt;/p&gt;
&lt;p&gt;Leave control.erap_ctl and control.clean as-is in the VMCS if VMRUN fails,
because as per AMD:&lt;/p&gt;
&lt;p&gt;there&amp;#39;s no explicit architectural guarantee about the behavior in the
  presence of VMRUN failures. So the best thing to do would be to assume
  that if VMRUN fails, the actions requested in the control fields may not
  have been performed.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-98714</guid>
    </item>
    <item>
      <title>GHSA-rrqj-3q8v-92j9</title>
      <link>https://db.gcve.eu/vuln/ghsa-rrqj-3q8v-92j9</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: SVM: Update control fields on #VMEXIT if and only if VMRUN succeeded&lt;/p&gt;
&lt;p&gt;Leave control.erap_ctl and control.clean as-is in the VMCS if VMRUN fails,
because as per AMD:&lt;/p&gt;
&lt;p&gt;there&amp;#39;s no explicit architectural guarantee about the behavior in the
  presence of VMRUN failures. So the best thing to do would be to assume
  that if VMRUN fails, the actions requested in the control fields may not
  have been performed.&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;KVM: SVM: Update control fields on #VMEXIT if and only if VMRUN succeeded&lt;/p&gt;
&lt;p&gt;Leave control.erap_ctl and control.clean as-is in the VMCS if VMRUN fails,
because as per AMD:&lt;/p&gt;
&lt;p&gt;there&amp;#39;s no explicit architectural guarantee about the behavior in the
  presence of VMRUN failures. So the best thing to do would be to assume
  that if VMRUN fails, the actions requested in the control fields may not
  have been performed.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-rrqj-3q8v-92j9</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-98714 — KVM: SVM: Update control fields on #VMEXIT if and only if VMRUN succeeded</title>
      <link>https://db.gcve.eu/vuln/msrc_cve-2026-98714</link>
      <description>msrc_CVE-2026-98714</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/msrc_cve-2026-98714</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98714</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2026-98714</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, 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 248 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Update control fields on #VMEXIT if and only if VMRUN succeeded Leave control.erap_ctl and control.clean as-is in the VMCS if VMRUN fails, because as per AMD:   there&amp;#39;s no explicit architectural guarantee about the behavior in the   presence of VMRUN failures. So the best thing to do would be to assume   that if VMRUN fails, the actions requested in the control fields may not   have been performed.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, 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 248 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Update control fields on #VMEXIT if and only if VMRUN succeeded Leave control.erap_ctl and control.clean as-is in the VMCS if VMRUN fails, because as per AMD:   there&amp;#39;s no explicit architectural guarantee about the behavior in the   presence of VMRUN failures. So the best thing to do would be to assume   that if VMRUN fails, the actions requested in the control fields may not   have been performed.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2026-98714</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4019 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4019</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2026-4019</guid>
    </item>
  </channel>
</rss>
