KVM: SEV: Pin source page for write when adding CPUID data for SNP guest
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 "correct" 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's unlikely for the CPUID information to be backed by a read-only mapping. [sean: rewrite shortlog and changelog, tag for stable@]
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 7.1.4
- CVEs
- CVE-2026-64285
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 23:12 UTC · Revision 1
Source evidence
KVM: SEV: Pin source page for write when adding CPUID data for SNP guest
core-osv · Original sourcePublished 25 Jul 2026, 08:49 UTC
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 "correct" 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's unlikely for the CPUID information to be backed by a read-only mapping. [sean: rewrite shortlog and changelog, tag for stable@]
osv:CVE-2026-64285
Kernel
Fixed versions: 7.1.4
Complete source record
{
"id": "b5cbf4fb372a7e1b365481a5893f4cc312ae0550460048475f15605e53da7c44",
"url": "https://osv.dev/vulnerability/CVE-2026-64285",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "KVM: SEV: Pin source page for write when adding CPUID data for SNP guest",
"summary": "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 \"correct\" 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's unlikely for the CPUID information to be backed by a read-only mapping. [sean: rewrite shortlog and changelog, tag for stable@]",
"evidence": "osv:CVE-2026-64285",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "7.1.4",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-64285",
"aliases": [
"CVE-2026-64285"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "2a62345b30529e488beb6a1220577b3495933724"
},
{
"fixed": "dcdb476f5fc5701ec06c23efe3e3529f07ca391e"
},
{
"fixed": "f13e900599089b10113ceb36013423f0837c6792"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-64285.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "7.0.0"
},
{
"fixed": "7.1.4"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-64285.json"
}
}
],
"modified": "2026-10-28T02:30:40.527440129Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/dcdb476f5fc5701ec06c23efe3e3529f07ca391e",
"https://git.kernel.org/stable/c/f13e900599089b10113ceb36013423f0837c6792",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/64xxx/CVE-2026-64285.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-64285",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/64xxx/CVE-2026-64285.json"
}
},
"related_cves": [
{
"value": "CVE-2026-64285",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 507907,
"published_at": "2026-07-25T08:49:26.898+00:00"
}