<?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://127.0.0.1:10001</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>Sat, 21 Nov 2026 04:33:22 +0000</lastBuildDate>
    <item>
      <title>certfr-2026-avi-0316 — De multiples vulnérabilités ont été découvertes dans les produits VMware. Elles permettent à un attaquant de provoquer…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-0316</link>
      <description>certfr-2026-avi-0316</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0316</guid>
    </item>
    <item>
      <title>OESA-2025-1872 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2025-1872</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: x86/mmu: Treat NX as a valid SPTE bit for NPT&lt;/p&gt;
&lt;p&gt;Treat the NX bit as valid when using NPT, as KVM will set the NX bit when
the NX huge page mitigation is enabled (mindblowing) and trigger the WARN
that fires on reserved SPTE bits being set.&lt;/p&gt;
&lt;p&gt;KVM has required NX support for SVM since commit b26a71a1a5b9 (&amp;amp;quot;KVM: SVM:
Refuse to load kvm_amd if NX support is not available&amp;amp;quot;) for exactly this
reason, but apparently it never occurred to anyone to actually test NPT
with the mitigation enabled.&lt;/p&gt;
&lt;p&gt;------------[ cut here ]------------
  spte = 0x800000018a600ee7, level = 2, rsvd bits = 0x800f0000001fe000
  WARNING: CPU: 152 PID: 15966 at arch/x86/kvm/mmu/spte.c:215 make_spte+0x327/0x340 [kvm]
  Hardware name: Google, Inc. Arcadia_IT_80/Arcadia_IT_80, BIOS 10.48.0 01/27/2022
  RIP: 0010:make_spte+0x327/0x340 [kvm]
  Call Trace:
   &amp;amp;lt;TASK&amp;amp;gt;
   tdp_mmu_map_handle_target_level+0xc3/0x230 [kvm]
   kvm_tdp_mmu_map+0x343/0x3b0 [kvm]
   direct_page_fault+0x1ae/0x2a0 [kvm]
   kvm_tdp_page_fault+0x7d/0x90 [kvm]
   kvm_mmu_page_fault+0xfb/0x2e0 [kvm]
   npf_interception+0x55/0x90 [kvm_amd]
   svm_invoke_exit_handler+0x31/0xf0 [kvm_amd]
   svm_handle_exit+0xf6/0x1d0 [kvm_amd]
   vcpu_enter_guest+0xb6d/0xee0 [kvm]
   ? kvm_pmu_trigger_event+0x6d/0x230 [kvm]
   vcpu_run+0x65/0x2c0 [kvm]
   kvm_arch_vcpu_ioctl_run+0x355/0x610 [kvm]
   kvm_vcpu…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: x86/mmu: Treat NX as a valid SPTE bit for NPT&lt;/p&gt;
&lt;p&gt;Treat the NX bit as valid when using NPT, as KVM will set the NX bit when
the NX huge page mitigation is enabled (mindblowing) and trigger the WARN
that fires on reserved SPTE bits being set.&lt;/p&gt;
&lt;p&gt;KVM has required NX support for SVM since commit b26a71a1a5b9 (&amp;amp;quot;KVM: SVM:
Refuse to load kvm_amd if NX support is not available&amp;amp;quot;) for exactly this
reason, but apparently it never occurred to anyone to actually test NPT
with the mitigation enabled.&lt;/p&gt;
&lt;p&gt;------------[ cut here ]------------
  spte = 0x800000018a600ee7, level = 2, rsvd bits = 0x800f0000001fe000
  WARNING: CPU: 152 PID: 15966 at arch/x86/kvm/mmu/spte.c:215 make_spte+0x327/0x340 [kvm]
  Hardware name: Google, Inc. Arcadia_IT_80/Arcadia_IT_80, BIOS 10.48.0 01/27/2022
  RIP: 0010:make_spte+0x327/0x340 [kvm]
  Call Trace:
   &amp;amp;lt;TASK&amp;amp;gt;
   tdp_mmu_map_handle_target_level+0xc3/0x230 [kvm]
   kvm_tdp_mmu_map+0x343/0x3b0 [kvm]
   direct_page_fault+0x1ae/0x2a0 [kvm]
   kvm_tdp_page_fault+0x7d/0x90 [kvm]
   kvm_mmu_page_fault+0xfb/0x2e0 [kvm]
   npf_interception+0x55/0x90 [kvm_amd]
   svm_invoke_exit_handler+0x31/0xf0 [kvm_amd]
   svm_handle_exit+0xf6/0x1d0 [kvm_amd]
   vcpu_enter_guest+0xb6d/0xee0 [kvm]
   ? kvm_pmu_trigger_event+0x6d/0x230 [kvm]
   vcpu_run+0x65/0x2c0 [kvm]
   kvm_arch_vcpu_ioctl_run+0x355/0x610 [kvm]
   kvm_vcpu…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2025-1872</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-50224</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2022-50224</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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, Ubuntu:16.04:LTS: linux-hwe-edge and 159 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: KVM: x86/mmu: Treat NX as a valid SPTE bit for NPT Treat the NX bit as valid when using NPT, as KVM will set the NX bit when the NX huge page mitigation is enabled (mindblowing) and trigger the WARN that fires on reserved SPTE bits being set. KVM has required NX support for SVM since commit b26a71a1a5b9 (&amp;#34;KVM: SVM: Refuse to load kvm_amd if NX support is not available&amp;#34;) for exactly this reason, but apparently it never occurred to anyone to actually test NPT with the mitigation enabled.   ------------[ cut here ]------------   spte = 0x800000018a600ee7, level = 2, rsvd bits = 0x800f0000001fe000   WARNING: CPU: 152 PID: 15966 at arch/x86/kvm/mmu/spte.c:215 make_spte+0x327/0x340 [kvm]   Hardware name: Google, Inc. Arcadia_IT_80/Arcadia_IT_80, BIOS 10.48.0 01/27/2022   RIP: 0010:make_spte+0x327/0x340 [kvm]   Call Trace:    &amp;lt;TASK&amp;gt;    tdp_mmu_map_handle_target_level+0xc3/0x230 [kvm]    kvm_tdp_mmu_map+0x343/0x3b0 [kvm]    direct_page_fault+0x1ae/0x2a0 [kvm]    kvm_tdp_page_fault+0x7d/0x90 [kvm]    kvm_mmu_page_fault+0xfb/0x2e0 [kvm]    npf_interception+0x55/0x90 [kvm_amd]    svm_invoke_exit_handler+0x31/0xf0 [kvm_amd]    svm_handle_exit+0xf6/0x1d0 [kvm_amd]    vcpu_enter_guest+0xb6d/0xee0 [kvm]    ? kvm_pmu_trigger_event+0x6d/0x230 [kvm]    vcpu_run+0x65/0x2c0 [kvm]    kvm_arch_vcpu_ioctl_run+0x355/0x610 [kvm]    kvm_vcpu_ioctl+0x551/0x610 [kvm]    __se_sys_ioctl+0x77/0xc0    __x64_sys_ioctl+0x1d/0x20    do_syscal…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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, Ubuntu:16.04:LTS: linux-hwe-edge and 159 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: KVM: x86/mmu: Treat NX as a valid SPTE bit for NPT Treat the NX bit as valid when using NPT, as KVM will set the NX bit when the NX huge page mitigation is enabled (mindblowing) and trigger the WARN that fires on reserved SPTE bits being set. KVM has required NX support for SVM since commit b26a71a1a5b9 (&amp;#34;KVM: SVM: Refuse to load kvm_amd if NX support is not available&amp;#34;) for exactly this reason, but apparently it never occurred to anyone to actually test NPT with the mitigation enabled.   ------------[ cut here ]------------   spte = 0x800000018a600ee7, level = 2, rsvd bits = 0x800f0000001fe000   WARNING: CPU: 152 PID: 15966 at arch/x86/kvm/mmu/spte.c:215 make_spte+0x327/0x340 [kvm]   Hardware name: Google, Inc. Arcadia_IT_80/Arcadia_IT_80, BIOS 10.48.0 01/27/2022   RIP: 0010:make_spte+0x327/0x340 [kvm]   Call Trace:    &amp;lt;TASK&amp;gt;    tdp_mmu_map_handle_target_level+0xc3/0x230 [kvm]    kvm_tdp_mmu_map+0x343/0x3b0 [kvm]    direct_page_fault+0x1ae/0x2a0 [kvm]    kvm_tdp_page_fault+0x7d/0x90 [kvm]    kvm_mmu_page_fault+0xfb/0x2e0 [kvm]    npf_interception+0x55/0x90 [kvm_amd]    svm_invoke_exit_handler+0x31/0xf0 [kvm_amd]    svm_handle_exit+0xf6/0x1d0 [kvm_amd]    vcpu_enter_guest+0xb6d/0xee0 [kvm]    ? kvm_pmu_trigger_event+0x6d/0x230 [kvm]    vcpu_run+0x65/0x2c0 [kvm]    kvm_arch_vcpu_ioctl_run+0x355/0x610 [kvm]    kvm_vcpu_ioctl+0x551/0x610 [kvm]    __se_sys_ioctl+0x77/0xc0    __x64_sys_ioctl+0x1d/0x20    do_syscal…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2022-50224</guid>
    </item>
  </channel>
</rss>
