<?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 00:51:22 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-31593</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-31593</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2026-31593</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0519 — De multiples vulnérabilités ont été découvertes dans Microsoft Azure Linux. Elles permettent à un attaquant de provoque…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-0519</link>
      <description>certfr-2026-avi-0519</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0519</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-31593</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-31593</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 118 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Reject attempts to sync VMSA of an already-launched/encrypted vCPU Reject synchronizing vCPU state to its associated VMSA if the vCPU has already been launched, i.e. if the VMSA has already been encrypted.  On a host with SNP enabled, accessing guest-private memory generates an RMP #PF and panics the host.   BUG: unable to handle page fault for address: ff1276cbfdf36000   #PF: supervisor write access in kernel mode   #PF: error_code(0x80000003) - RMP violation   PGD 5a31801067 P4D 5a31802067 PUD 40ccfb5063 PMD 40e5954063 PTE 80000040fdf36163   SEV-SNP: PFN 0x40fdf36, RMP entry: [0x6010fffffffff001 - 0x000000000000001f]   Oops: Oops: 0003 [#1] SMP NOPTI   CPU: 33 UID: 0 PID: 996180 Comm: qemu-system-x86 Tainted: G           OE   Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE   Hardware name: Dell Inc. PowerEdge R7625/0H1TJT, BIOS 1.5.8 07/21/2023   RIP: 0010:sev_es_sync_vmsa+0x54/0x4c0 [kvm_amd]   Call Trace:    &amp;lt;TASK&amp;gt;    snp_launch_update_vmsa+0x19d/0x290 [kvm_amd]    snp_launch_finish+0xb6/0x380 [kvm_amd]    sev_mem_enc_ioctl+0x14e/0x720 [kvm_amd]    kvm_arch_vm_ioctl+0x837/0xcf0 [kvm]    kvm_vm_ioctl+0x3fd/0xcc0 [kvm]    __x64_sys_ioctl+0xa3/0x100    x64_sys_call+0xfe0/0x2350    do_syscall_64+0x81/0x10f0    entry_SYSCALL_64_after_hwframe+0x76/0x7e   RIP: 0033:0x7ffff673287d    &amp;lt;/TASK&amp;gt; Note, the KVM flaw has been present since commit ad73109ae7ec (&amp;#34;KVM: SVM: Provide support to launch and run an SEV-…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 118 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Reject attempts to sync VMSA of an already-launched/encrypted vCPU Reject synchronizing vCPU state to its associated VMSA if the vCPU has already been launched, i.e. if the VMSA has already been encrypted.  On a host with SNP enabled, accessing guest-private memory generates an RMP #PF and panics the host.   BUG: unable to handle page fault for address: ff1276cbfdf36000   #PF: supervisor write access in kernel mode   #PF: error_code(0x80000003) - RMP violation   PGD 5a31801067 P4D 5a31802067 PUD 40ccfb5063 PMD 40e5954063 PTE 80000040fdf36163   SEV-SNP: PFN 0x40fdf36, RMP entry: [0x6010fffffffff001 - 0x000000000000001f]   Oops: Oops: 0003 [#1] SMP NOPTI   CPU: 33 UID: 0 PID: 996180 Comm: qemu-system-x86 Tainted: G           OE   Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE   Hardware name: Dell Inc. PowerEdge R7625/0H1TJT, BIOS 1.5.8 07/21/2023   RIP: 0010:sev_es_sync_vmsa+0x54/0x4c0 [kvm_amd]   Call Trace:    &amp;lt;TASK&amp;gt;    snp_launch_update_vmsa+0x19d/0x290 [kvm_amd]    snp_launch_finish+0xb6/0x380 [kvm_amd]    sev_mem_enc_ioctl+0x14e/0x720 [kvm_amd]    kvm_arch_vm_ioctl+0x837/0xcf0 [kvm]    kvm_vm_ioctl+0x3fd/0xcc0 [kvm]    __x64_sys_ioctl+0xa3/0x100    x64_sys_call+0xfe0/0x2350    do_syscall_64+0x81/0x10f0    entry_SYSCALL_64_after_hwframe+0x76/0x7e   RIP: 0033:0x7ffff673287d    &amp;lt;/TASK&amp;gt; Note, the KVM flaw has been present since commit ad73109ae7ec (&amp;#34;KVM: SVM: Provide support to launch and run an SEV-…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-31593</guid>
    </item>
  </channel>
</rss>
