https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 05:29:00 +0000 https://vulnerability.circl.lu/vuln/cve-2026-64285 <p><strong>Affected:</strong> Linux</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> <p><strong>Affected:</strong> Linux</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/cve-2026-64285