{"api_version":"1","generated_at":"2026-07-26T00:27:46+00:00","cve":"CVE-2026-64285","urls":{"html":"https://cve.report/CVE-2026-64285","api":"https://cve.report/api/cve/CVE-2026-64285.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-64285","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-64285"},"summary":{"title":"KVM: SEV: Pin source page for write when adding CPUID data for SNP guest","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SEV: Pin source page for write when adding CPUID data for SNP guest\n\nWhen populating a guest_memfd instance with the initial CPUID data for an\nSNP guest, acquire a writable pin on the source page as KVM will write back\nthe \"correct\" CPUID information if the userspace provided data is rejected\nby trusted firmware.  Because KVM writes to the source page using a kernel\nmapping, pinning for read could result in KVM clobbering read-only memory.\n\nNote, well-behaved VMMs are unlikely to be affected, as CPUID information\nis almost always dynamically generated by userspace, i.e. it's unlikely for\nthe CPUID information to be backed by a read-only mapping.\n\n[sean: rewrite shortlog and changelog, tag for stable@]","state":"PUBLISHED","assigner":"Linux","published_at":"2026-07-25 10:17:09","updated_at":"2026-07-25 10:17:09"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/f13e900599089b10113ceb36013423f0837c6792","name":"https://git.kernel.org/stable/c/f13e900599089b10113ceb36013423f0837c6792","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/dcdb476f5fc5701ec06c23efe3e3529f07ca391e","name":"https://git.kernel.org/stable/c/dcdb476f5fc5701ec06c23efe3e3529f07ca391e","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-64285","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64285","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 2a62345b30529e488beb6a1220577b3495933724 dcdb476f5fc5701ec06c23efe3e3529f07ca391e git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 2a62345b30529e488beb6a1220577b3495933724 f13e900599089b10113ceb36013423f0837c6792 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 7.0","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.0 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.4 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"64285","cve":"CVE-2026-64285","epss":"0.001980000","percentile":"0.097860000","score_date":"2026-07-25","updated_at":"2026-07-26 00:12:33"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["arch/x86/kvm/svm/sev.c","arch/x86/kvm/vmx/tdx.c","include/linux/kvm_host.h","virt/kvm/guest_memfd.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"dcdb476f5fc5701ec06c23efe3e3529f07ca391e","status":"affected","version":"2a62345b30529e488beb6a1220577b3495933724","versionType":"git"},{"lessThan":"f13e900599089b10113ceb36013423f0837c6792","status":"affected","version":"2a62345b30529e488beb6a1220577b3495933724","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["arch/x86/kvm/svm/sev.c","arch/x86/kvm/vmx/tdx.c","include/linux/kvm_host.h","virt/kvm/guest_memfd.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"7.0"},{"lessThan":"7.0","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"7.1.*","status":"unaffected","version":"7.1.4","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.2-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.4","versionStartIncluding":"7.0","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2-rc1","versionStartIncluding":"7.0","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SEV: Pin source page for write when adding CPUID data for SNP guest\n\nWhen populating a guest_memfd instance with the initial CPUID data for an\nSNP guest, acquire a writable pin on the source page as KVM will write back\nthe \"correct\" CPUID information if the userspace provided data is rejected\nby trusted firmware.  Because KVM writes to the source page using a kernel\nmapping, pinning for read could result in KVM clobbering read-only memory.\n\nNote, well-behaved VMMs are unlikely to be affected, as CPUID information\nis almost always dynamically generated by userspace, i.e. it's unlikely for\nthe CPUID information to be backed by a read-only mapping.\n\n[sean: rewrite shortlog and changelog, tag for stable@]"}],"providerMetadata":{"dateUpdated":"2026-07-25T08:49:26.898Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/dcdb476f5fc5701ec06c23efe3e3529f07ca391e"},{"url":"https://git.kernel.org/stable/c/f13e900599089b10113ceb36013423f0837c6792"}],"title":"KVM: SEV: Pin source page for write when adding CPUID data for SNP guest","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-64285","datePublished":"2026-07-25T08:49:26.898Z","dateReserved":"2026-07-19T15:36:31.777Z","dateUpdated":"2026-07-25T08:49:26.898Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-07-25 10:17:09","lastModifiedDate":"2026-07-25 10:17:09","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"64285","Ordinal":"1","Title":"KVM: SEV: Pin source page for write when adding CPUID data for S","CVE":"CVE-2026-64285","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"64285","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SEV: Pin source page for write when adding CPUID data for SNP guest\n\nWhen populating a guest_memfd instance with the initial CPUID data for an\nSNP guest, acquire a writable pin on the source page as KVM will write back\nthe \"correct\" CPUID information if the userspace provided data is rejected\nby trusted firmware.  Because KVM writes to the source page using a kernel\nmapping, pinning for read could result in KVM clobbering read-only memory.\n\nNote, well-behaved VMMs are unlikely to be affected, as CPUID information\nis almost always dynamically generated by userspace, i.e. it's unlikely for\nthe CPUID information to be backed by a read-only mapping.\n\n[sean: rewrite shortlog and changelog, tag for stable@]","Type":"Description","Title":"KVM: SEV: Pin source page for write when adding CPUID data for S"}]}}}