<?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:09:19 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99745</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99745</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;x86/bugs: Select the BHI mitigation based on the attack vector properly&lt;/p&gt;
&lt;p&gt;The BHI mitigation selection is inconsistent with the documentation
(attack_vector_controls.rst), which lists BHI under both the
user-&amp;gt;kernel and guest-&amp;gt;host attack vectors. bhi_select_mitigation()
only enables it when CPU_MITIGATE_GUEST_HOST is set; otherwise it
selects BHI_MITIGATION_OFF, even if CPU_MITIGATE_USER_KERNEL is set.&lt;/p&gt;
&lt;p&gt;As a result, a kernel compiled with KVM disabled gets BHI automatically
disabled, since CPU_MITIGATE_GUEST_HOST defaults to off without KVM.
This is a bug, given that CPU_MITIGATE_USER_KERNEL still needs it: on
affected Intel CPUs these kernels lose BHI_DIS_S or the BHB clearing
loop by default. Booting with mitigations=auto,no_guest_host has the
same effect.&lt;/p&gt;
&lt;p&gt;Select BHI_MITIGATION_ON whenever user-&amp;gt;kernel is mitigated, and keep
BHI_MITIGATION_VMEXIT_ONLY for the guest-&amp;gt;host-only case.&lt;/p&gt;
&lt;p&gt;[ bp: Clarify commit title. ]&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;x86/bugs: Select the BHI mitigation based on the attack vector properly&lt;/p&gt;
&lt;p&gt;The BHI mitigation selection is inconsistent with the documentation
(attack_vector_controls.rst), which lists BHI under both the
user-&amp;gt;kernel and guest-&amp;gt;host attack vectors. bhi_select_mitigation()
only enables it when CPU_MITIGATE_GUEST_HOST is set; otherwise it
selects BHI_MITIGATION_OFF, even if CPU_MITIGATE_USER_KERNEL is set.&lt;/p&gt;
&lt;p&gt;As a result, a kernel compiled with KVM disabled gets BHI automatically
disabled, since CPU_MITIGATE_GUEST_HOST defaults to off without KVM.
This is a bug, given that CPU_MITIGATE_USER_KERNEL still needs it: on
affected Intel CPUs these kernels lose BHI_DIS_S or the BHB clearing
loop by default. Booting with mitigations=auto,no_guest_host has the
same effect.&lt;/p&gt;
&lt;p&gt;Select BHI_MITIGATION_ON whenever user-&amp;gt;kernel is mitigated, and keep
BHI_MITIGATION_VMEXIT_ONLY for the guest-&amp;gt;host-only case.&lt;/p&gt;
&lt;p&gt;[ bp: Clarify commit title. ]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99745</guid>
    </item>
    <item>
      <title>GHSA-x7q5-8hv5-rv8m</title>
      <link>https://db.gcve.eu/vuln/ghsa-x7q5-8hv5-rv8m</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;x86/bugs: Select the BHI mitigation based on the attack vector properly&lt;/p&gt;
&lt;p&gt;The BHI mitigation selection is inconsistent with the documentation
(attack_vector_controls.rst), which lists BHI under both the
user-&amp;gt;kernel and guest-&amp;gt;host attack vectors. bhi_select_mitigation()
only enables it when CPU_MITIGATE_GUEST_HOST is set; otherwise it
selects BHI_MITIGATION_OFF, even if CPU_MITIGATE_USER_KERNEL is set.&lt;/p&gt;
&lt;p&gt;As a result, a kernel compiled with KVM disabled gets BHI automatically
disabled, since CPU_MITIGATE_GUEST_HOST defaults to off without KVM.
This is a bug, given that CPU_MITIGATE_USER_KERNEL still needs it: on
affected Intel CPUs these kernels lose BHI_DIS_S or the BHB clearing
loop by default. Booting with mitigations=auto,no_guest_host has the
same effect.&lt;/p&gt;
&lt;p&gt;Select BHI_MITIGATION_ON whenever user-&amp;gt;kernel is mitigated, and keep
BHI_MITIGATION_VMEXIT_ONLY for the guest-&amp;gt;host-only case.&lt;/p&gt;
&lt;p&gt;[ bp: Clarify commit title. ]&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;x86/bugs: Select the BHI mitigation based on the attack vector properly&lt;/p&gt;
&lt;p&gt;The BHI mitigation selection is inconsistent with the documentation
(attack_vector_controls.rst), which lists BHI under both the
user-&amp;gt;kernel and guest-&amp;gt;host attack vectors. bhi_select_mitigation()
only enables it when CPU_MITIGATE_GUEST_HOST is set; otherwise it
selects BHI_MITIGATION_OFF, even if CPU_MITIGATE_USER_KERNEL is set.&lt;/p&gt;
&lt;p&gt;As a result, a kernel compiled with KVM disabled gets BHI automatically
disabled, since CPU_MITIGATE_GUEST_HOST defaults to off without KVM.
This is a bug, given that CPU_MITIGATE_USER_KERNEL still needs it: on
affected Intel CPUs these kernels lose BHI_DIS_S or the BHB clearing
loop by default. Booting with mitigations=auto,no_guest_host has the
same effect.&lt;/p&gt;
&lt;p&gt;Select BHI_MITIGATION_ON whenever user-&amp;gt;kernel is mitigated, and keep
BHI_MITIGATION_VMEXIT_ONLY for the guest-&amp;gt;host-only case.&lt;/p&gt;
&lt;p&gt;[ bp: Clarify commit title. ]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-x7q5-8hv5-rv8m</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>
