https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 01 Oct 2026 22:35:23 +0000 https://vulnerability.circl.lu/vuln/bell-cve-2026-64285 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Withdrawn by the publisher.</strong></p> https://vulnerability.circl.lu/vuln/bell-cve-2026-64285 https://vulnerability.circl.lu/vuln/certfr-2026-avi-1162 certfr-2026-avi-1162 https://vulnerability.circl.lu/vuln/certfr-2026-avi-1162 https://vulnerability.circl.lu/vuln/fkie_cve-2026-64285 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>KVM: SEV: Pin source page for write when adding CPUID data for SNP guest</p> <p>When populating a guest_memfd instance with the initial CPUID data for an SNP guest, acquire a writable pin on the source page as KVM will write back the &#34;correct&#34; CPUID information if the userspace provided data is rejected by trusted firmware. Because KVM writes to the source page using a kernel mapping, pinning for read could result in KVM clobbering read-only memory.</p> <p>Note, well-behaved VMMs are unlikely to be affected, as CPUID information is almost always dynamically generated by userspace, i.e. it&#39;s unlikely for the CPUID information to be backed by a read-only mapping.</p> <p>[sean: rewrite shortlog and changelog, tag for stable@]</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>KVM: SEV: Pin source page for write when adding CPUID data for SNP guest</p> <p>When populating a guest_memfd instance with the initial CPUID data for an SNP guest, acquire a writable pin on the source page as KVM will write back the &#34;correct&#34; CPUID information if the userspace provided data is rejected by trusted firmware. Because KVM writes to the source page using a kernel mapping, pinning for read could result in KVM clobbering read-only memory.</p> <p>Note, well-behaved VMMs are unlikely to be affected, as CPUID information is almost always dynamically generated by userspace, i.e. it&#39;s unlikely for the CPUID information to be backed by a read-only mapping.</p> <p>[sean: rewrite shortlog and changelog, tag for stable@]</p> https://vulnerability.circl.lu/vuln/fkie_cve-2026-64285 https://vulnerability.circl.lu/vuln/ghsa-9frv-wmxv-xpwj <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>KVM: SEV: Pin source page for write when adding CPUID data for SNP guest</p> <p>When populating a guest_memfd instance with the initial CPUID data for an SNP guest, acquire a writable pin on the source page as KVM will write back the &#34;correct&#34; CPUID information if the userspace provided data is rejected by trusted firmware. Because KVM writes to the source page using a kernel mapping, pinning for read could result in KVM clobbering read-only memory.</p> <p>Note, well-behaved VMMs are unlikely to be affected, as CPUID information is almost always dynamically generated by userspace, i.e. it&#39;s unlikely for the CPUID information to be backed by a read-only mapping.</p> <p>[sean: rewrite shortlog and changelog, tag for stable@]</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>KVM: SEV: Pin source page for write when adding CPUID data for SNP guest</p> <p>When populating a guest_memfd instance with the initial CPUID data for an SNP guest, acquire a writable pin on the source page as KVM will write back the &#34;correct&#34; CPUID information if the userspace provided data is rejected by trusted firmware. Because KVM writes to the source page using a kernel mapping, pinning for read could result in KVM clobbering read-only memory.</p> <p>Note, well-behaved VMMs are unlikely to be affected, as CPUID information is almost always dynamically generated by userspace, i.e. it&#39;s unlikely for the CPUID information to be backed by a read-only mapping.</p> <p>[sean: rewrite shortlog and changelog, tag for stable@]</p> https://vulnerability.circl.lu/vuln/ghsa-9frv-wmxv-xpwj https://vulnerability.circl.lu/vuln/opensuse-su-2026:11476-1 <p>kernel-devel-7.1.7-1.1 on GA media</p> <p>kernel-devel-7.1.7-1.1 on GA media</p> https://vulnerability.circl.lu/vuln/opensuse-su-2026:11476-1 https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-64285 <p><strong>Affected:</strong> 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 112 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Pin source page for write when adding CPUID data for SNP guest When populating a guest_memfd instance with the initial CPUID data for an SNP guest, acquire a writable pin on the source page as KVM will write back the &#34;correct&#34; CPUID information if the userspace provided data is rejected by trusted firmware. Because KVM writes to the source page using a kernel mapping, pinning for read could result in KVM clobbering read-only memory. Note, well-behaved VMMs are unlikely to be affected, as CPUID information is almost always dynamically generated by userspace, i.e. it&#39;s unlikely for the CPUID information to be backed by a read-only mapping. [sean: rewrite shortlog and changelog, tag for stable@]</p> <p><strong>Affected:</strong> 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 112 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Pin source page for write when adding CPUID data for SNP guest When populating a guest_memfd instance with the initial CPUID data for an SNP guest, acquire a writable pin on the source page as KVM will write back the &#34;correct&#34; CPUID information if the userspace provided data is rejected by trusted firmware. Because KVM writes to the source page using a kernel mapping, pinning for read could result in KVM clobbering read-only memory. Note, well-behaved VMMs are unlikely to be affected, as CPUID information is almost always dynamically generated by userspace, i.e. it&#39;s unlikely for the CPUID information to be backed by a read-only mapping. [sean: rewrite shortlog and changelog, tag for stable@]</p> https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-64285 https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2527 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, dazu können DoS-Angriffe, die Offenlegung von Informationen, die Beschädigung des Speichers oder die Umgehung von Sicherheitsmaßnahmen gehören.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, dazu können DoS-Angriffe, die Offenlegung von Informationen, die Beschädigung des Speichers oder die Umgehung von Sicherheitsmaßnahmen gehören.</p> https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2527