<?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:44 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99338</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99338</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: TDX: Enable Notify VM exit&lt;/p&gt;
&lt;p&gt;Enable Notify VM exit functionality for TDX guests.&lt;/p&gt;
&lt;p&gt;Notify VM exit is an existing feature supported by KVM.  Userspace can
enable Notify VM exit through KVM_CAP_X86_NOTIFY_VMEXIT 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 Notify VM exit for TDX guests by:&lt;/p&gt;
&lt;p&gt;- Invoking TDX module API calls to set NOTIFY_VM_EXITING and Notify
    Window in TD VMCS.  It&amp;#39;s done in tdx_vcpu_init() where other TD VMCS
    bits are set.  Since TDX vCPU cannot be reset, it only needs to be
    configured once when initializing the TDX vCPU.&lt;/p&gt;
&lt;p&gt;- Adding corresponding exit handler for TDX Notify VM Exit.&lt;/p&gt;
&lt;p&gt;Notify VM exit can happen when executing the IRET instruction.  If the
IRET unblocks the NMI blocking state, bit 12 of the exit qualification
is set.  In this case, the VMM needs to restore the &amp;#34;blocked by NMI&amp;#34; state
when it decides to re-enter the guest.  For TDX, KVM cannot manage the
GUEST_INTERRUPTIBILITY_INFO and it&amp;#39;s TDX module&amp;#39;s responsibility to
handle it.  Extract the common part without NMI blocking handling into a
helper in common.h so that…&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 Notify VM exit&lt;/p&gt;
&lt;p&gt;Enable Notify VM exit functionality for TDX guests.&lt;/p&gt;
&lt;p&gt;Notify VM exit is an existing feature supported by KVM.  Userspace can
enable Notify VM exit through KVM_CAP_X86_NOTIFY_VMEXIT 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 Notify VM exit for TDX guests by:&lt;/p&gt;
&lt;p&gt;- Invoking TDX module API calls to set NOTIFY_VM_EXITING and Notify
    Window in TD VMCS.  It&amp;#39;s done in tdx_vcpu_init() where other TD VMCS
    bits are set.  Since TDX vCPU cannot be reset, it only needs to be
    configured once when initializing the TDX vCPU.&lt;/p&gt;
&lt;p&gt;- Adding corresponding exit handler for TDX Notify VM Exit.&lt;/p&gt;
&lt;p&gt;Notify VM exit can happen when executing the IRET instruction.  If the
IRET unblocks the NMI blocking state, bit 12 of the exit qualification
is set.  In this case, the VMM needs to restore the &amp;#34;blocked by NMI&amp;#34; state
when it decides to re-enter the guest.  For TDX, KVM cannot manage the
GUEST_INTERRUPTIBILITY_INFO and it&amp;#39;s TDX module&amp;#39;s responsibility to
handle it.  Extract the common part without NMI blocking handling into a
helper in common.h so that…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99338</guid>
    </item>
    <item>
      <title>GHSA-pc86-g3cq-2wv4</title>
      <link>https://db.gcve.eu/vuln/ghsa-pc86-g3cq-2wv4</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: TDX: Enable Notify VM exit&lt;/p&gt;
&lt;p&gt;Enable Notify VM exit functionality for TDX guests.&lt;/p&gt;
&lt;p&gt;Notify VM exit is an existing feature supported by KVM.  Userspace can
enable Notify VM exit through KVM_CAP_X86_NOTIFY_VMEXIT 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 Notify VM exit for TDX guests by:&lt;/p&gt;
&lt;p&gt;- Invoking TDX module API calls to set NOTIFY_VM_EXITING and Notify
    Window in TD VMCS.  It&amp;#39;s done in tdx_vcpu_init() where other TD VMCS
    bits are set.  Since TDX vCPU cannot be reset, it only needs to be
    configured once when initializing the TDX vCPU.&lt;/p&gt;
&lt;p&gt;- Adding corresponding exit handler for TDX Notify VM Exit.&lt;/p&gt;
&lt;p&gt;Notify VM exit can happen when executing the IRET instruction.  If the
IRET unblocks the NMI blocking state, bit 12 of the exit qualification
is set.  In this case, the VMM needs to restore the &amp;#34;blocked by NMI&amp;#34; state
when it decides to re-enter the guest.  For TDX, KVM cannot manage the
GUEST_INTERRUPTIBILITY_INFO and it&amp;#39;s TDX module&amp;#39;s responsibility to
handle it.  Extract the common part without NMI blocking handling into a
helper in common.h so that…&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 Notify VM exit&lt;/p&gt;
&lt;p&gt;Enable Notify VM exit functionality for TDX guests.&lt;/p&gt;
&lt;p&gt;Notify VM exit is an existing feature supported by KVM.  Userspace can
enable Notify VM exit through KVM_CAP_X86_NOTIFY_VMEXIT 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 Notify VM exit for TDX guests by:&lt;/p&gt;
&lt;p&gt;- Invoking TDX module API calls to set NOTIFY_VM_EXITING and Notify
    Window in TD VMCS.  It&amp;#39;s done in tdx_vcpu_init() where other TD VMCS
    bits are set.  Since TDX vCPU cannot be reset, it only needs to be
    configured once when initializing the TDX vCPU.&lt;/p&gt;
&lt;p&gt;- Adding corresponding exit handler for TDX Notify VM Exit.&lt;/p&gt;
&lt;p&gt;Notify VM exit can happen when executing the IRET instruction.  If the
IRET unblocks the NMI blocking state, bit 12 of the exit qualification
is set.  In this case, the VMM needs to restore the &amp;#34;blocked by NMI&amp;#34; state
when it decides to re-enter the guest.  For TDX, KVM cannot manage the
GUEST_INTERRUPTIBILITY_INFO and it&amp;#39;s TDX module&amp;#39;s responsibility to
handle it.  Extract the common part without NMI blocking handling into a
helper in common.h so that…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-pc86-g3cq-2wv4</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>
