CVE-2024-46689

MEDIUM EPSS 14.4%
Published Sep 13, 20241y ago · Modified Jun 17, 20261w ago
5.5 CVSS 3.1
Medium
Find Similar
Published Sep 13, 2024 1y ago
Last Modified Jun 17, 2026 1w ago

Description

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.

CVSS Details

Base Score
5.5
Exploitability
1.8
Impact
3.6
Vector string
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Attack Vector Local
Attack Complexity Low
Privileges Required Low
User Interaction None
Scope Unchanged
Confidentiality None
Integrity None
Availability High

Threat Intelligence

EPSS Exploit Probability
14.4% percentile
Exploit & Patch Status
No Known Exploit
Patch Available

Weaknesses 1

CWE-787 Out-of-bounds Write Memory Safety

Affected Products 11

VendorProductVersionRange
linuxlinux_kernel*≥4.18  –  <5.4.283
linuxlinux_kernel*≥5.5  –  <5.10.225
linuxlinux_kernel*≥5.11  –  <5.15.166
linuxlinux_kernel*≥5.16  –  <6.1.108
linuxlinux_kernel*≥6.2  –  <6.6.49
linuxlinux_kernel*≥6.7  –  <6.10.8
linuxlinux_kernel6.11any
linuxlinux_kernel6.11any
linuxlinux_kernel6.11any
linuxlinux_kernel6.11any
linuxlinux_kernel6.11any

References 9

  • git.kernel.org https://git.kernel.org/stable/c/0ee9594c974368a17e85a431e9fe1c14fb65c278
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/62c2d63605ca25b5db78a347ed303c0a0a77d5b4
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/d9d48d70e922b272875cda60d2ada89291c840cf
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/eaff392c1e34fb77cc61505a31b0191e5e46e271
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/ef80520be0ff78ae5ed44cb6eee1525e65bebe70
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/f5a5a5a0e95f36e2792d48e6e4b64e665eb01374
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/f9bb896eab221618927ae6a2f1d566567999839d
    Patch
  • lists.debian.org https://lists.debian.org/debian-lts-announce/2024/10/msg00003.html
  • lists.debian.org https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html

Remediation

  • git.kernel.org https://git.kernel.org/stable/c/0ee9594c974368a17e85a431e9fe1c14fb65c278
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/62c2d63605ca25b5db78a347ed303c0a0a77d5b4
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/d9d48d70e922b272875cda60d2ada89291c840cf
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/eaff392c1e34fb77cc61505a31b0191e5e46e271
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/ef80520be0ff78ae5ed44cb6eee1525e65bebe70
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/f5a5a5a0e95f36e2792d48e6e4b64e665eb01374
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/f9bb896eab221618927ae6a2f1d566567999839d
    Patch