CVE-2026-98638 (GCVE-0-2026-98638)
Vulnerability from cvelistv5
Published
2026-10-18 15:20
Modified
2026-10-19 09:23
Severity ?
VLAI Severity ?
EPSS score ?
Summary
In the Linux kernel, the following vulnerability has been resolved:
KVM: arm64: Validate the SVE vector length in pkvm_vcpu_init_sve()
pkvm_vcpu_init_sve() clamps only the upper bound of the host-provided
sve_max_vl, so an invalid vector length reaches sve_state_size_from_vl()
and the WARN_ON() there, which is fatal at EL2. The existing
!sve_state_size test rejects such a length, but only after the macro has
run.
Check sve_vl_valid() before deriving the state size. A valid length
cannot yield a zero size, so the !sve_state_size test goes with it.
References
Impacted products
{
"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": "faf66e55e87498ab4bf88cdf9a629e61b3f2d3bc",
"status": "affected",
"version": "5db1bef933427aa467ad89c7b695a84a6b4afe16",
"versionType": "git"
},
{
"lessThan": "bae3e4493046de4fefa15f809d9b8dc114e84a3d",
"status": "affected",
"version": "5db1bef933427aa467ad89c7b695a84a6b4afe16",
"versionType": "git"
},
{
"lessThan": "2a2eb10795a1e495aebc7f829ccecb72c05b4fd9",
"status": "affected",
"version": "5db1bef933427aa467ad89c7b695a84a6b4afe16",
"versionType": "git"
}
]
},
{
"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": [
{
"status": "affected",
"version": "6.16"
},
{
"lessThan": "6.16",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.55",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.2.*",
"status": "unaffected",
"version": "7.2.9",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.3",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.55",
"versionStartIncluding": "6.16",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.2.9",
"versionStartIncluding": "6.16",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.3",
"versionStartIncluding": "6.16",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: arm64: Validate the SVE vector length in pkvm_vcpu_init_sve()\n\npkvm_vcpu_init_sve() clamps only the upper bound of the host-provided\nsve_max_vl, so an invalid vector length reaches sve_state_size_from_vl()\nand the WARN_ON() there, which is fatal at EL2. The existing\n!sve_state_size test rejects such a length, but only after the macro has\nrun.\n\nCheck sve_vl_valid() before deriving the state size. A valid length\ncannot yield a zero size, so the !sve_state_size test goes with it."
}
],
"providerMetadata": {
"dateUpdated": "2026-10-19T09:23:08.052Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/faf66e55e87498ab4bf88cdf9a629e61b3f2d3bc"
},
{
"url": "https://git.kernel.org/stable/c/bae3e4493046de4fefa15f809d9b8dc114e84a3d"
},
{
"url": "https://git.kernel.org/stable/c/2a2eb10795a1e495aebc7f829ccecb72c05b4fd9"
}
],
"title": "KVM: arm64: Validate the SVE vector length in pkvm_vcpu_init_sve()",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-98638",
"datePublished": "2026-10-18T15:20:09.380Z",
"dateReserved": "2026-09-25T10:25:14.361Z",
"dateUpdated": "2026-10-19T09:23:08.052Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…
Loading…