<?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>Fri, 20 Nov 2026 21:03:45 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99337</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99337</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: TDX: Enable Bus Lock VM exit&lt;/p&gt;
&lt;p&gt;Enable Bus Lock VM exit functionality for TDX guests.&lt;/p&gt;
&lt;p&gt;Bus Lock VM exit is an existing feature supported by KVM.  Userspace can
enable Bus Lock VM exit through KVM_BUS_LOCK_DETECTION_EXIT when it&amp;#39;s
reported as supported.  However, KVM reports the support of this CAP
just based on the hardware capability but doesn&amp;#39;t differentiate between
VMX and TDX.  This leads to the issue that userspace can enable this cap
for TDX guests without getting an error, but the feature is not actually
enabled because KVM doesn&amp;#39;t call the TDX module API to program the
relevant TD VMCS fields.&lt;/p&gt;
&lt;p&gt;Enable Bus Lock VM exit for TDX guests by programming the
BUS_LOCK_DETECTION control in the TD VMCS and by adding the exit handler.&lt;/p&gt;
&lt;p&gt;Note, there is no enumeration bit for this feature by TDX module because
all TDX modules support it and allow to set the TD VMCS as long as the
hardware supports the feature.&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: TDX: Enable Bus Lock VM exit&lt;/p&gt;
&lt;p&gt;Enable Bus Lock VM exit functionality for TDX guests.&lt;/p&gt;
&lt;p&gt;Bus Lock VM exit is an existing feature supported by KVM.  Userspace can
enable Bus Lock VM exit through KVM_BUS_LOCK_DETECTION_EXIT when it&amp;#39;s
reported as supported.  However, KVM reports the support of this CAP
just based on the hardware capability but doesn&amp;#39;t differentiate between
VMX and TDX.  This leads to the issue that userspace can enable this cap
for TDX guests without getting an error, but the feature is not actually
enabled because KVM doesn&amp;#39;t call the TDX module API to program the
relevant TD VMCS fields.&lt;/p&gt;
&lt;p&gt;Enable Bus Lock VM exit for TDX guests by programming the
BUS_LOCK_DETECTION control in the TD VMCS and by adding the exit handler.&lt;/p&gt;
&lt;p&gt;Note, there is no enumeration bit for this feature by TDX module because
all TDX modules support it and allow to set the TD VMCS as long as the
hardware supports the feature.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99337</guid>
    </item>
    <item>
      <title>GHSA-f9h5-wpxf-58ww</title>
      <link>https://db.gcve.eu/vuln/ghsa-f9h5-wpxf-58ww</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: TDX: Enable Bus Lock VM exit&lt;/p&gt;
&lt;p&gt;Enable Bus Lock VM exit functionality for TDX guests.&lt;/p&gt;
&lt;p&gt;Bus Lock VM exit is an existing feature supported by KVM.  Userspace can
enable Bus Lock VM exit through KVM_BUS_LOCK_DETECTION_EXIT when it&amp;#39;s
reported as supported.  However, KVM reports the support of this CAP
just based on the hardware capability but doesn&amp;#39;t differentiate between
VMX and TDX.  This leads to the issue that userspace can enable this cap
for TDX guests without getting an error, but the feature is not actually
enabled because KVM doesn&amp;#39;t call the TDX module API to program the
relevant TD VMCS fields.&lt;/p&gt;
&lt;p&gt;Enable Bus Lock VM exit for TDX guests by programming the
BUS_LOCK_DETECTION control in the TD VMCS and by adding the exit handler.&lt;/p&gt;
&lt;p&gt;Note, there is no enumeration bit for this feature by TDX module because
all TDX modules support it and allow to set the TD VMCS as long as the
hardware supports the feature.&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: TDX: Enable Bus Lock VM exit&lt;/p&gt;
&lt;p&gt;Enable Bus Lock VM exit functionality for TDX guests.&lt;/p&gt;
&lt;p&gt;Bus Lock VM exit is an existing feature supported by KVM.  Userspace can
enable Bus Lock VM exit through KVM_BUS_LOCK_DETECTION_EXIT when it&amp;#39;s
reported as supported.  However, KVM reports the support of this CAP
just based on the hardware capability but doesn&amp;#39;t differentiate between
VMX and TDX.  This leads to the issue that userspace can enable this cap
for TDX guests without getting an error, but the feature is not actually
enabled because KVM doesn&amp;#39;t call the TDX module API to program the
relevant TD VMCS fields.&lt;/p&gt;
&lt;p&gt;Enable Bus Lock VM exit for TDX guests by programming the
BUS_LOCK_DETECTION control in the TD VMCS and by adding the exit handler.&lt;/p&gt;
&lt;p&gt;Note, there is no enumeration bit for this feature by TDX module because
all TDX modules support it and allow to set the TD VMCS as long as the
hardware supports the feature.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-f9h5-wpxf-58ww</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-99337 — KVM: TDX: Enable Bus Lock VM exit</title>
      <link>https://db.gcve.eu/vuln/msrc_cve-2026-99337</link>
      <description>msrc_CVE-2026-99337</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/msrc_cve-2026-99337</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4695 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4695</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-4695</guid>
    </item>
  </channel>
</rss>
