CVE-2026-46147 (GCVE-0-2026-46147)
Vulnerability from cvelistv5 – Published: 2026-05-28 09:36 – Updated: 2026-06-14 17:58
VLAI
EPSS
VEX
Title
KVM: arm64: Fix pin leak and publication ordering in __pkvm_init_vcpu()
Summary
In the Linux kernel, the following vulnerability has been resolved:
KVM: arm64: Fix pin leak and publication ordering in __pkvm_init_vcpu()
Two bugs exist in the vCPU initialisation path:
1. If a check fails after hyp_pin_shared_mem() succeeds, the cleanup
path jumps to 'unlock' without calling unpin_host_vcpu() or
unpin_host_sve_state(), permanently leaking pin references on the
host vCPU and SVE state pages.
Extract a register_hyp_vcpu() helper that performs the checks and
the store. When register_hyp_vcpu() returns an error, call
unpin_host_vcpu() and unpin_host_sve_state() inline before falling
through to the existing 'unlock' label.
2. register_hyp_vcpu() publishes the new vCPU pointer into
'hyp_vm->vcpus[]' with a bare store, allowing a concurrent caller
of pkvm_load_hyp_vcpu() to observe a partially initialised vCPU
object.
Ensure the store uses smp_store_release() and the load uses
smp_load_acquire(). While 'vm_table_lock' currently serialises the
store and the load, these barriers ensure the reader sees the fully
initialised 'hyp_vcpu' object even if there were a lockless path or
if the lock's own ordering guarantees were insufficient for nested
object initialization.
Severity
5.5 (Medium)
Assigner
References
Impacted products
2 products
| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 , < 7d3c27b54253cda91dc4d2c1bfc109c490837ab9
(git)
Affected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 , < 6d69c0ed978f7f0efd053fc98390f25ab77c1aea (git) Affected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 , < 73b9c1e5da84cd69b1a86e374e450817cd051371 (git) Affected: 0 , < 6.18.30 (semver) Affected: 0 , < 7.0.7 (semver) |
guessed | |
| Linux | Linux |
Unaffected:
6.18.30 , ≤ 6.18.*
(semver)
Unaffected: 7.0.7 , ≤ 7.0.* (semver) Unaffected: 7.1 , ≤ * (original_commit_for_fix) |
guessed |
{
"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",
"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",
"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 \u0027unlock\u0027 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 \u0027unlock\u0027 label.\n\n2. register_hyp_vcpu() publishes the new vCPU pointer into\n \u0027hyp_vm-\u003evcpus[]\u0027 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 \u0027vm_table_lock\u0027 currently serialises the\n store and the load, these barriers ensure the reader sees the fully\n initialised \u0027hyp_vcpu\u0027 object even if there were a lockless path or\n if the lock\u0027s own ordering guarantees were insufficient for nested\n object initialization."
}
],
"providerMetadata": {
"dateUpdated": "2026-06-14T17:58:03.230Z",
"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-06-14T17:58:03.230Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-46147",
"date": "2026-09-15",
"epss": "0.00126",
"percentile": "0.02627"
},
"microsoft_vex": {
"current_release_date": "2026-08-10T14:56:33.000Z",
"cve": "CVE-2026-46147",
"id": "msrc_CVE-2026-46147",
"initial_release_date": "2026-05-29T01:07:53.000Z",
"product_status:known_affected": "6",
"source": "Microsoft CSAF VEX",
"status": "final",
"title": "KVM: arm64: Fix pin leak and publication ordering in __pkvm_init_vcpu()",
"url": "https://msrc.microsoft.com/csaf/vex/2026/msrc_cve-2026-46147.json",
"version": "7"
},
"nvd": "{\"cve\":{\"id\":\"CVE-2026-46147\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2026-05-28T10:16:30.320\",\"lastModified\":\"2026-06-17T10:53:08.980\",\"vulnStatus\":\"Analyzed\",\"cveTags\":[],\"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 \u0027unlock\u0027 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 \u0027unlock\u0027 label.\\n\\n2. register_hyp_vcpu() publishes the new vCPU pointer into\\n \u0027hyp_vm-\u003evcpus[]\u0027 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 \u0027vm_table_lock\u0027 currently serialises the\\n store and the load, these barriers ensure the reader sees the fully\\n initialised \u0027hyp_vcpu\u0027 object even if there were a lockless path or\\n if the lock\u0027s own ordering guarantees were insufficient for nested\\n object initialization.\"}],\"affected\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"affectedData\":[{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"unaffected\",\"programFiles\":[\"arch/arm64/kvm/hyp/nvhe/pkvm.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"1da177e4c3f41524e886b7f1b8a0c1fc7321cac2\",\"lessThan\":\"7d3c27b54253cda91dc4d2c1bfc109c490837ab9\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"1da177e4c3f41524e886b7f1b8a0c1fc7321cac2\",\"lessThan\":\"6d69c0ed978f7f0efd053fc98390f25ab77c1aea\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"1da177e4c3f41524e886b7f1b8a0c1fc7321cac2\",\"lessThan\":\"73b9c1e5da84cd69b1a86e374e450817cd051371\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"0\",\"lessThan\":\"6.18.30\",\"versionType\":\"semver\",\"status\":\"affected\"},{\"version\":\"0\",\"lessThan\":\"7.0.7\",\"versionType\":\"semver\",\"status\":\"affected\"}]},{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"affected\",\"programFiles\":[\"arch/arm64/kvm/hyp/nvhe/pkvm.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"6.18.30\",\"lessThanOrEqual\":\"6.18.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"7.0.7\",\"lessThanOrEqual\":\"7.0.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"7.1\",\"lessThanOrEqual\":\"*\",\"versionType\":\"original_commit_for_fix\",\"status\":\"unaffected\"}]}]}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\",\"baseScore\":5.5,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.8,\"impactScore\":3.6}]},\"weaknesses\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-401\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionEndExcluding\":\"6.18.30\",\"matchCriteriaId\":\"B2F7049B-B157-4797-BBC1-82A75717CDEC\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.19\",\"versionEndExcluding\":\"7.0.7\",\"matchCriteriaId\":\"D0893CA7-9AE6-4DFE-AC75-48967D73AD8E\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:*\",\"matchCriteriaId\":\"B1EF7059-E670-45F4-B422-54C40FA86390\"}]}]}],\"references\":[{\"url\":\"https://git.kernel.org/stable/c/6d69c0ed978f7f0efd053fc98390f25ab77c1aea\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/73b9c1e5da84cd69b1a86e374e450817cd051371\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/7d3c27b54253cda91dc4d2c1bfc109c490837ab9\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]}]}}",
"redhat_vex": {
"aggregate_severity": "None",
"current_release_date": "2026-06-28T07:41:04+00:00",
"cve": "CVE-2026-46147",
"id": "CVE-2026-46147",
"initial_release_date": "2026-05-28T00:00:00+00:00",
"product_status:known_not_affected": "274",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: KVM: arm64: Fix pin leak and publication ordering in __pkvm_init_vcpu()",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-46147.json",
"version": "3"
},
"suse_vex": {
"aggregate_severity": "moderate",
"current_release_date": "2026-09-11T01:12:00Z",
"cve": "CVE-2026-46147",
"id": "CVE-2026-46147",
"initial_release_date": "2026-05-29T01:16:17Z",
"product_status:first_fixed": "2",
"product_status:known_affected": "453",
"product_status:known_not_affected": "279",
"product_status:recommended": "254",
"source": "SUSE CSAF VEX",
"status": "interim",
"title": "SUSE CVE CVE-2026-46147",
"url": "https://ftp.suse.com/pub/projects/security/csaf-vex/cve-2026-46147.json",
"version": "13"
}
}
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Loading…
Loading…