{"api_version":"1","generated_at":"2026-05-31T07:54:58+00:00","cve":"CVE-2026-46147","urls":{"html":"https://cve.report/CVE-2026-46147","api":"https://cve.report/api/cve/CVE-2026-46147.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-46147","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-46147"},"summary":{"title":"KVM: arm64: Fix pin leak and publication ordering in __pkvm_init_vcpu()","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: arm64: Fix pin leak and publication ordering in __pkvm_init_vcpu()\n\nTwo bugs exist in the vCPU initialisation path:\n\n1. If a check fails after hyp_pin_shared_mem() succeeds, the cleanup\n   path jumps to 'unlock' without calling unpin_host_vcpu() or\n   unpin_host_sve_state(), permanently leaking pin references on the\n   host vCPU and SVE state pages.\n\n   Extract a register_hyp_vcpu() helper that performs the checks and\n   the store. When register_hyp_vcpu() returns an error, call\n   unpin_host_vcpu() and unpin_host_sve_state() inline before falling\n   through to the existing 'unlock' label.\n\n2. register_hyp_vcpu() publishes the new vCPU pointer into\n   'hyp_vm->vcpus[]' with a bare store, allowing a concurrent caller\n   of pkvm_load_hyp_vcpu() to observe a partially initialised vCPU\n   object.\n\n   Ensure the store uses smp_store_release() and the load uses\n   smp_load_acquire(). While 'vm_table_lock' currently serialises the\n   store and the load, these barriers ensure the reader sees the fully\n   initialised 'hyp_vcpu' object even if there were a lockless path or\n   if the lock's own ordering guarantees were insufficient for nested\n   object initialization.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-05-28 10:16:30","updated_at":"2026-05-28 13:44:01"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/7d3c27b54253cda91dc4d2c1bfc109c490837ab9","name":"https://git.kernel.org/stable/c/7d3c27b54253cda91dc4d2c1bfc109c490837ab9","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/73b9c1e5da84cd69b1a86e374e450817cd051371","name":"https://git.kernel.org/stable/c/73b9c1e5da84cd69b1a86e374e450817cd051371","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/6d69c0ed978f7f0efd053fc98390f25ab77c1aea","name":"https://git.kernel.org/stable/c/6d69c0ed978f7f0efd053fc98390f25ab77c1aea","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-46147","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46147","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 7d3c27b54253cda91dc4d2c1bfc109c490837ab9 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 6d69c0ed978f7f0efd053fc98390f25ab77c1aea git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 73b9c1e5da84cd69b1a86e374e450817cd051371 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.18.30 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 7.0.7 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.30 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.0.7 7.0.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1-rc2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"46147","cve":"CVE-2026-46147","epss":"0.000170000","percentile":"0.043550000","score_date":"2026-05-30","updated_at":"2026-05-31 00:14:03"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["arch/arm64/kvm/hyp/nvhe/pkvm.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"7d3c27b54253cda91dc4d2c1bfc109c490837ab9","status":"affected","version":"1da177e4c3f41524e886b7f1b8a0c1fc7321cac2","versionType":"git"},{"lessThan":"6d69c0ed978f7f0efd053fc98390f25ab77c1aea","status":"affected","version":"1da177e4c3f41524e886b7f1b8a0c1fc7321cac2","versionType":"git"},{"lessThan":"73b9c1e5da84cd69b1a86e374e450817cd051371","status":"affected","version":"1da177e4c3f41524e886b7f1b8a0c1fc7321cac2","versionType":"git"},{"lessThan":"6.18.30","status":"affected","version":"0","versionType":"semver"},{"lessThan":"7.0.7","status":"affected","version":"0","versionType":"semver"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["arch/arm64/kvm/hyp/nvhe/pkvm.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.30","versionType":"semver"},{"lessThanOrEqual":"7.0.*","status":"unaffected","version":"7.0.7","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.1-rc2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.30","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.0.7","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1-rc2","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: arm64: Fix pin leak and publication ordering in __pkvm_init_vcpu()\n\nTwo bugs exist in the vCPU initialisation path:\n\n1. If a check fails after hyp_pin_shared_mem() succeeds, the cleanup\n   path jumps to 'unlock' without calling unpin_host_vcpu() or\n   unpin_host_sve_state(), permanently leaking pin references on the\n   host vCPU and SVE state pages.\n\n   Extract a register_hyp_vcpu() helper that performs the checks and\n   the store. When register_hyp_vcpu() returns an error, call\n   unpin_host_vcpu() and unpin_host_sve_state() inline before falling\n   through to the existing 'unlock' label.\n\n2. register_hyp_vcpu() publishes the new vCPU pointer into\n   'hyp_vm->vcpus[]' with a bare store, allowing a concurrent caller\n   of pkvm_load_hyp_vcpu() to observe a partially initialised vCPU\n   object.\n\n   Ensure the store uses smp_store_release() and the load uses\n   smp_load_acquire(). While 'vm_table_lock' currently serialises the\n   store and the load, these barriers ensure the reader sees the fully\n   initialised 'hyp_vcpu' object even if there were a lockless path or\n   if the lock's own ordering guarantees were insufficient for nested\n   object initialization."}],"providerMetadata":{"dateUpdated":"2026-05-28T09:36:03.892Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/7d3c27b54253cda91dc4d2c1bfc109c490837ab9"},{"url":"https://git.kernel.org/stable/c/6d69c0ed978f7f0efd053fc98390f25ab77c1aea"},{"url":"https://git.kernel.org/stable/c/73b9c1e5da84cd69b1a86e374e450817cd051371"}],"title":"KVM: arm64: Fix pin leak and publication ordering in __pkvm_init_vcpu()","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-46147","datePublished":"2026-05-28T09:36:03.892Z","dateReserved":"2026-05-13T15:03:33.101Z","dateUpdated":"2026-05-28T09:36:03.892Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-05-28 10:16:30","lastModifiedDate":"2026-05-28 13:44:01","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"46147","Ordinal":"1","Title":"KVM: arm64: Fix pin leak and publication ordering in __pkvm_init","CVE":"CVE-2026-46147","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"46147","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: arm64: Fix pin leak and publication ordering in __pkvm_init_vcpu()\n\nTwo bugs exist in the vCPU initialisation path:\n\n1. If a check fails after hyp_pin_shared_mem() succeeds, the cleanup\n   path jumps to 'unlock' without calling unpin_host_vcpu() or\n   unpin_host_sve_state(), permanently leaking pin references on the\n   host vCPU and SVE state pages.\n\n   Extract a register_hyp_vcpu() helper that performs the checks and\n   the store. When register_hyp_vcpu() returns an error, call\n   unpin_host_vcpu() and unpin_host_sve_state() inline before falling\n   through to the existing 'unlock' label.\n\n2. register_hyp_vcpu() publishes the new vCPU pointer into\n   'hyp_vm->vcpus[]' with a bare store, allowing a concurrent caller\n   of pkvm_load_hyp_vcpu() to observe a partially initialised vCPU\n   object.\n\n   Ensure the store uses smp_store_release() and the load uses\n   smp_load_acquire(). While 'vm_table_lock' currently serialises the\n   store and the load, these barriers ensure the reader sees the fully\n   initialised 'hyp_vcpu' object even if there were a lockless path or\n   if the lock's own ordering guarantees were insufficient for nested\n   object initialization.","Type":"Description","Title":"KVM: arm64: Fix pin leak and publication ordering in __pkvm_init"}]}}}