soc: qcom: cmd-db: Map shared memory as WC, not WB
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 312416d9171a1460b7ed8d182b5b540c910ce80d · < 62c2d63605ca25b5db78a347ed303c0a0a77d5b4| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
soc: qcom: cmd-db: Map shared memory as WC, not WB
Linux does not write into cmd-db region. This region of memory is write protected by XPU. XPU may sometime falsely detect clean cache eviction as "write" into the write protected region leading to secure interrupt which causes an endless loop somewhere in Trust Zone.
The only reason it is working right now is because Qualcomm Hypervisor maps the same region as Non-Cacheable memory in Stage 2 translation tables. The issue manifests if we want to use another hypervisor (like Xen or KVM), which does not know anything about those specific mappings.
Changing the mapping of cmd-db memory from MEMREMAP_WB to MEMREMAP_WT/WC removes dependency on correct mappings in Stage 2 tables. This patch fixes the issue by updating the mapping to MEMREMAP_WC.
I tested this on SA8155P with Xen.
From the CVE record · Linux
The Linux kernel maps Qualcomm cmd-db shared memory as write-back, which can cause XPU to mistake a clean cache eviction for a write. This can trigger a secure interrupt and an endless loop when a hypervisor such as Xen or KVM does not provide the specific Stage 2 mapping used by the Qualcomm Hypervisor. The input does not describe an attacker path or authentication or user-interaction requirements.
Engineers running Linux kernels with Qualcomm cmd-db on systems using a hypervisor other than the Qualcomm Hypervisor should check their kernels; affected versions were not provided.