{
  "public_date" : "2026-05-28T00:00:00Z",
  "bugzilla" : {
    "description" : "kernel: KVM: arm64: Fix pin leak and publication ordering in __pkvm_init_vcpu()",
    "id" : "2482620",
    "url" : "https://bugzilla.redhat.com/show_bug.cgi?id=2482620"
  },
  "cwe" : "CWE-772",
  "details" : [ "In the Linux kernel, the following vulnerability has been resolved:\nKVM: arm64: Fix pin leak and publication ordering in __pkvm_init_vcpu()\nTwo bugs exist in the vCPU initialisation path:\n1. If a check fails after hyp_pin_shared_mem() succeeds, the cleanup\npath jumps to 'unlock' without calling unpin_host_vcpu() or\nunpin_host_sve_state(), permanently leaking pin references on the\nhost vCPU and SVE state pages.\nExtract a register_hyp_vcpu() helper that performs the checks and\nthe store. When register_hyp_vcpu() returns an error, call\nunpin_host_vcpu() and unpin_host_sve_state() inline before falling\nthrough to the existing 'unlock' label.\n2. register_hyp_vcpu() publishes the new vCPU pointer into\n'hyp_vm->vcpus[]' with a bare store, allowing a concurrent caller\nof pkvm_load_hyp_vcpu() to observe a partially initialised vCPU\nobject.\nEnsure the store uses smp_store_release() and the load uses\nsmp_load_acquire(). While 'vm_table_lock' currently serialises the\nstore and the load, these barriers ensure the reader sees the fully\ninitialised 'hyp_vcpu' object even if there were a lockless path or\nif the lock's own ordering guarantees were insufficient for nested\nobject initialization.", "A flaw was found in the Linux kernel's Kernel-based Virtual Machine (KVM) for ARM64 architectures. During the vCPU initialization process, a pin leak can occur, leading to a permanent loss of references to host vCPU and SVE state pages. Additionally, a concurrent process might observe a partially initialized vCPU object due to improper publication ordering. These issues could lead to resource exhaustion and system instability, potentially resulting in a denial of service." ],
  "package_state" : [ {
    "product_name" : "Red Hat Enterprise Linux 10",
    "fix_state" : "Not affected",
    "package_name" : "kernel",
    "cpe" : "cpe:/o:redhat:enterprise_linux:10"
  }, {
    "product_name" : "Red Hat Enterprise Linux 6",
    "fix_state" : "Not affected",
    "package_name" : "kernel",
    "cpe" : "cpe:/o:redhat:enterprise_linux:6"
  }, {
    "product_name" : "Red Hat Enterprise Linux 7",
    "fix_state" : "Not affected",
    "package_name" : "kernel",
    "cpe" : "cpe:/o:redhat:enterprise_linux:7"
  }, {
    "product_name" : "Red Hat Enterprise Linux 7",
    "fix_state" : "Not affected",
    "package_name" : "kernel-rt",
    "cpe" : "cpe:/o:redhat:enterprise_linux:7"
  }, {
    "product_name" : "Red Hat Enterprise Linux 8",
    "fix_state" : "Not affected",
    "package_name" : "kernel",
    "cpe" : "cpe:/o:redhat:enterprise_linux:8"
  }, {
    "product_name" : "Red Hat Enterprise Linux 8",
    "fix_state" : "Not affected",
    "package_name" : "kernel-rt",
    "cpe" : "cpe:/o:redhat:enterprise_linux:8"
  }, {
    "product_name" : "Red Hat Enterprise Linux 9",
    "fix_state" : "Not affected",
    "package_name" : "kernel",
    "cpe" : "cpe:/o:redhat:enterprise_linux:9"
  }, {
    "product_name" : "Red Hat Enterprise Linux 9",
    "fix_state" : "Not affected",
    "package_name" : "kernel-rt",
    "cpe" : "cpe:/o:redhat:enterprise_linux:9"
  } ],
  "references" : [ "https://www.cve.org/CVERecord?id=CVE-2026-46147\nhttps://nvd.nist.gov/vuln/detail/CVE-2026-46147\nhttps://lore.kernel.org/linux-cve-announce/2026052821-CVE-2026-46147-9b7f@gregkh/T" ],
  "name" : "CVE-2026-46147",
  "csaw" : false
}