KVM: arm64: Validate the SVE vector length in pkvm_vcpu_init_sve()
CVSS score
—
EPSS probability
%0.2
Risk score
—
Published
1 d ago
Resmî kaynaklarda yeterli kanıt bulunamadı. Bu sonuç “yama yok” anlamına gelmez.
Impact on My Inventory
Only the personal products you have added to your account are assessed; an organisation's inventory does not appear here.
Checking session…
Vulnerability description
CVE AI research
DayBreach AI Explanation
Verified against sourcesSources read
2
Source agreement
Tam uyum
Evidence confidence
%63
Short explanation
In the Linux kernel, the KVM arm64 module’s pkvm_vcpu_init_sve function only clamps the upper bound of the host‑provided sve_max_vl. An invalid vector length can trigger a WARN_ON at EL2, causing a kernel crash. (S0,S1)
A fatal kernel panic at EL2 can bring the entire system down, resulting in loss of availability. (S0)
What should be done?
- Monitor vendor advisories and apply patches when released
- Add explicit SVE vector length validation in unpatched kernels
- Consider upgrading from affected kernel revisions (5db1bef… < 2a2eb107…)
Chain of evidence and sources
Bu güvenlik açığı, Linux çekirdeğinin KVM arm64 bileşeninde pkvm_vcpu_init_sve işlevinde SVE vektör uzunluğunun yetersiz doğrulanmasından kaynaklanmaktadır. (S0)
Geçersiz bir vektör uzunluğu, WARN_ON() tetikleyerek EL2 seviyesinde çekirdek çökmesine yol açar; bu, sistemin tamamen çökmesine neden olabilir. (S0,S1)
Resmi kaynaklarda yama durumu doğrulanamadı; yama mevcut olup olmadığı belirsizdir. (S0)
Show the technical text from the sources
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.
Explanation produced with the local gemini-flash-lite-latest model. Numerical metrics and the KEV, patch and exploit statuses are not determined by AI.
IMPACT: Affected Products and Software
RED HAT CSAF/VEX: Product Impact Check
SCORING: CVSS from Multiple Sources
CVSS Scores
The Common Vulnerability Scoring System is a standardised framework for assessing the severity of vulnerabilities in software and systems. We collect and display CVSS scores from several sources for each CVE.
| SCORE | VERSION | SEVERITY | VECTOR | SOURCE |
|---|---|---|---|---|
| The sources have not yet published a verified CVSS metric. | ||||
Patch and Remediation Guide
Solution & Remediation Advisory
İncelenen resmî kaynaklarda yama durumu doğrulanamadı. Bu sonuç “yama yok” anlamına gelmez.
Public exploit and active exploitation status
Verified exploit intelligence
No verified public PoC, exploit repository or Metasploit module has been found for this CVE yet.
Weakness Classification and Attack Patterns (CWE & CAPEC)
CWE - Common Weakness Enumeration
While CVE identifies specific instances of vulnerabilities, CWE categorises the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-98638 is associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-98638 weaknesses.
Official Sources and Advisories
Yama durumu bilinmiyor
Similar Vulnerabilities
Get this vulnerability through the API
Affected products, version ranges, exploitation status and patch information in a single request, with a free key.
curl -H "x-api-key: $DAYBREACH_API_KEY" \ "https://api.daybreach.dev/api/v1/intel/cves/CVE-2026-98638"