KVM: arm64: Validate the SVE vector length in pkvm_vcpu_init_sve()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.18.55, 7.2.9
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 5db1bef933427aa467ad89c7b695a84a6b4afe16 · fixed in faf66e55e87498ab4bf88cdf9a629e61b3f2d3bc; From 5db1bef933427aa467ad89c7b695a84a6b4afe16 · fixed in bae3e4493046de4fefa15f809d9b8dc114e84a3d; From 5db1bef933427aa467ad89c7b695a84a6b4afe16 · fixed in 2a2eb10795a1e495aebc7f829ccecb72c05b4fd9
- Linux Linux
6.16
- KernelLinux
From 6.16.0 · fixed in 6.18.55; From 6.19.0 · fixed in 7.2.9