KVM: arm64: Apply the fine-grained UNDEFs without FEAT_FGT
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
KVM: arm64: Apply the fine-grained UNDEFs without FEAT_FGT
FGUs don't actually require hardware support, so don't gate fgt trap config insertion on FGT. This is the only action required to allow FGUs always, as kvm_calculate_traps() already computes the FGU bits with or without FEAT_FGT.
This also fixes a spurious WARN when a TLBI OS is run on a guest in vEL1 without FEAT_TLBIOS on non FEAT_FGT hardware. In this configuration the course-grained HCR_EL2.TTLBOS trap reaches the handler handle_tlbi_el1(), which expects an EL1 TLBI only from vEL2. With FGUs enabled the UNDEF will be injected without needing the specific handler.
[oliver: Take Wei-Lin's suggested changelog]
From the CVE record · Linux
KVM on arm64 does not apply fine-grained undefined-instruction traps when FEAT_FGT is absent, even though those traps do not require hardware support. A guest running a TLBI OS instruction at vEL1 without FEAT_TLBIOS on hardware without FEAT_FGT can trigger a spurious kernel warning; the input does not establish whether authentication or user interaction is required.
Operators running the Linux kernel with KVM on arm64 should check affected versions against the vendor advisory; no version range is provided.