CVE-2024-46689: soc: qcom: cmd-db: Map shared memory as WC, not WB
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.25% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0ee9594c974368a17e85a431e9fe1c14fb65c278, 62c2d63605ca25b5db78a347ed303c0a0a77d5b4, d9d48d70e922b272875cda60d2ada89291c840cf.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 0ee9594c974368a17e85a431e9fe1c14fb65c278, 62c2d63605ca25b5db78a347ed303c0a0a77d5b4, d9d48d70e922b272875cda60d2ada89291c840cf or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 13, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 16th percentile
- CWE
- CWE-787
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.18 and later · before 5.4.283
- linux linux kernel5.5 and later · before 5.10.225
- linux linux kernel5.11 and later · before 5.15.166
- linux linux kernel5.16 and later · before 6.1.108
- linux linux kernel6.2 and later · before 6.6.49
- linux linux kernel6.7 and later · before 6.10.8
- linux linux kernel6.11
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.18affected
- 312416d9171a1460b7ed8d182b5b540c910ce80d and later · before 0ee9594c974368a17e85a431e9fe1c14fb65c278affected · git
- 312416d9171a1460b7ed8d182b5b540c910ce80d and later · before f5a5a5a0e95f36e2792d48e6e4b64e665eb01374affected · git
- 312416d9171a1460b7ed8d182b5b540c910ce80d and later · before eaff392c1e34fb77cc61505a31b0191e5e46e271affected · git
- 312416d9171a1460b7ed8d182b5b540c910ce80d and later · before d9d48d70e922b272875cda60d2ada89291c840cfaffected · git
- 312416d9171a1460b7ed8d182b5b540c910ce80d and later · before ef80520be0ff78ae5ed44cb6eee1525e65bebe70affected · git
- 312416d9171a1460b7ed8d182b5b540c910ce80d and later · before 62c2d63605ca25b5db78a347ed303c0a0a77d5b4affected · git
- 312416d9171a1460b7ed8d182b5b540c910ce80d and later · before f9bb896eab221618927ae6a2f1d566567999839daffected · git
- before 4.18not affected · semver
- 5.4.283 and later · up to and including 5.4.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:9 | kernel | before 5.14.0-611.5.1.el9_7 | 5.14.0-611.5.1.el9_7 |
| AlmaLinux:9 | kernel-64k | before 5.14.0-611.5.1.el9_7 | 5.14.0-611.5.1.el9_7 |
| AlmaLinux:9 | kernel-64k-core | before 5.14.0-611.5.1.el9_7 | 5.14.0-611.5.1.el9_7 |
| AlmaLinux:9 | kernel-64k-debug | before 5.14.0-611.5.1.el9_7 | 5.14.0-611.5.1.el9_7 |
| AlmaLinux:9 | kernel-64k-debug-core | before 5.14.0-611.5.1.el9_7 | 5.14.0-611.5.1.el9_7 |
| AlmaLinux:9 | kernel-64k-debug-devel | before 5.14.0-611.5.1.el9_7 | 5.14.0-611.5.1.el9_7 |
| AlmaLinux:9 | kernel-64k-debug-devel-matched | before 5.14.0-611.5.1.el9_7 | 5.14.0-611.5.1.el9_7 |
| AlmaLinux:9 | kernel-64k-debug-modules | before 5.14.0-611.5.1.el9_7 | 5.14.0-611.5.1.el9_7 |
| AlmaLinux:9 | kernel-64k-debug-modules-core | before 5.14.0-611.5.1.el9_7 | 5.14.0-611.5.1.el9_7 |
| AlmaLinux:9 | kernel-64k-debug-modules-extra | before 5.14.0-611.5.1.el9_7 | 5.14.0-611.5.1.el9_7 |
| AlmaLinux:9 | kernel-64k-devel | before 5.14.0-611.5.1.el9_7 | 5.14.0-611.5.1.el9_7 |
| AlmaLinux:9 | kernel-64k-devel-matched | before 5.14.0-611.5.1.el9_7 | 5.14.0-611.5.1.el9_7 |
| AlmaLinux:9 | kernel-64k-modules | before 5.14.0-611.5.1.el9_7 | 5.14.0-611.5.1.el9_7 |
| AlmaLinux:9 | kernel-64k-modules-core | before 5.14.0-611.5.1.el9_7 | 5.14.0-611.5.1.el9_7 |
| AlmaLinux:9 | kernel-64k-modules-extra | before 5.14.0-611.5.1.el9_7 | 5.14.0-611.5.1.el9_7 |
| AlmaLinux:9 | kernel-abi-stablelists | before 5.14.0-611.5.1.el9_7 | 5.14.0-611.5.1.el9_7 |
| AlmaLinux:9 | kernel-core | before 5.14.0-611.5.1.el9_7 | 5.14.0-611.5.1.el9_7 |
| AlmaLinux:9 | kernel-cross-headers | before 5.14.0-611.5.1.el9_7 | 5.14.0-611.5.1.el9_7 |
| AlmaLinux:9 | kernel-debug | before 5.14.0-611.5.1.el9_7 | 5.14.0-611.5.1.el9_7 |
| AlmaLinux:9 | kernel-debug-core | before 5.14.0-611.5.1.el9_7 | 5.14.0-611.5.1.el9_7 |
| AlmaLinux:9 | kernel-debug-devel | before 5.14.0-611.5.1.el9_7 | 5.14.0-611.5.1.el9_7 |
| AlmaLinux:9 | kernel-debug-devel-matched | before 5.14.0-611.5.1.el9_7 | 5.14.0-611.5.1.el9_7 |
| AlmaLinux:9 | kernel-debug-modules | before 5.14.0-611.5.1.el9_7 | 5.14.0-611.5.1.el9_7 |
| AlmaLinux:9 | kernel-debug-modules-core | before 5.14.0-611.5.1.el9_7 | 5.14.0-611.5.1.el9_7 |
+53
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-46687Sep 13, 2024 · btrfs: fix a use-after-free when hitting errors inside btrfs_submit_chunk()31Monitor
- ← EarlierCVE-2024-46688Sep 13, 2024 · erofs: fix out-of-bound access when z_erofs_gbuf_growsize() partially fails22Monitor
- Later →CVE-2024-46690Sep 13, 2024 · nfsd: fix nfsd4_deleg_getattr_conflict in presence of third party lease22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0ee9594c974368a17e85a431e9fe1c14fb65c278 | Vendor (CNA) |
| Linux Linux | 62c2d63605ca25b5db78a347ed303c0a0a77d5b4 | Vendor (CNA) |
| Linux Linux | d9d48d70e922b272875cda60d2ada89291c840cf | Vendor (CNA) |
| Linux Linux | eaff392c1e34fb77cc61505a31b0191e5e46e271 | Vendor (CNA) |
| Linux Linux | ef80520be0ff78ae5ed44cb6eee1525e65bebe70 | Vendor (CNA) |
| Linux Linux | f5a5a5a0e95f36e2792d48e6e4b64e665eb01374 | Vendor (CNA) |
| Linux Linux | f9bb896eab221618927ae6a2f1d566567999839d | Vendor (CNA) |
| almalinux:kernel | 5.14.0-611.5.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-611.5.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-611.5.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-611.5.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-611.5.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 5.14.0-611.5.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 5.14.0-611.5.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-611.5.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-611.5.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-611.5.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 5.14.0-611.5.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 5.14.0-611.5.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| debian:linux | 6.1.112-1 · Debian:12 | Package registry (OSV) |
| rocky linux:kernel | 0:5.14.0-611.5.1.el9_7 · Rocky Linux:9 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-1468 · Sep 16, 2024(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-787 · Out-of-bounds WriteCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/62c2d63605ca25b5db78a347ed303c0a0a77d5b4
- git.kernel.org/stable/c/d9d48d70e922b272875cda60d2ada89291c840cf
- git.kernel.org/stable/c/eaff392c1e34fb77cc61505a31b0191e5e46e271
- git.kernel.org/stable/c/ef80520be0ff78ae5ed44cb6eee1525e65bebe70
- git.kernel.org/stable/c/f5a5a5a0e95f36e2792d48e6e4b64e665eb01374
- git.kernel.org/stable/c/f9bb896eab221618927ae6a2f1d566567999839d
- lists.debian.org/debian-lts-announce/2024/10/msg00003.html
- lists.debian.org/debian-lts-announce/2025/01/msg00001.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.