CWE · MITRE source
CWE-1260Improper Handling of Overlap Between Protected Memory Ranges
The product allows address regions to overlap, which can result in the bypassing of intended memory protection.
Isolated memory regions and access control (read/write) policies are used by hardware to protect privileged software. Software components are often allowed to change or remap memory region definitions in order to enable flexible and dynamically changeable memory management by system software. If a software component running at lower privilege can program a memory address region to overlap with other memory regions used by software running at higher privilege, privilege escalation may be available to attackers. The memory protection unit (MPU) logic can incorrectly handle such an address overlap and allow the lower-privilege software to read or write into the protected memory region, resulting in privilege escalation attack. An address overlap weakness can also be used to launch a denial of service attack on the higher-privilege software memory regions.
Last updated: 04 July 2026 11:13 UTC
Cumulative inbound coverage
How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.
Collective: partial · 3 mapping(s) from 2 framework(s): CAPEC 2 (partial) · ATT&CK 1 (partial)
NIST 800-53 r5 controls that address this weakness (0)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
| No NIST controls proposed yet. | |||
MITRE ATT&CK techniques this weakness enables
Our own two-way CWE↔ATT&CK cross-walk — a direct mapping with no public source (the CWE→CAPEC→ATT&CK chain leaves most top weaknesses, incl. XSS and SQLi, mapped to nothing). Drafted by Grok and spot-checked by Claude Opus 4.8.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial).
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2024-4778 | 7.0 | 9.8 | 0.0044 | 2024-05-14 |
CVE-2019-1164 | 5.5 | 7.8 | 0.0094 | 2019-08-14 |
CVE-2022-27813 | 5.5 | 8.1 | 0.0018 | 2023-10-19 |
CVE-2025-1937 | 5.5 | 7.5 | 0.0052 | 2025-03-04 |
CVE-2025-22889 UPD | 5.5 | 7.9 | 0.0014 | 2025-08-12 |
CVE-2019-25559 | 3.5 | 5.5 | 0.0017 | 2026-03-21 |
CVE-2019-25570 | 3.5 | 5.5 | 0.0022 | 2026-03-21 |
CVE-2019-25572 | 3.5 | 6.2 | 0.0016 | 2026-03-21 |
CVE-2019-25585 | 3.5 | 6.2 | 0.0018 | 2026-03-22 |
CVE-2019-25592 | 3.5 | 6.2 | 0.0016 | 2026-03-22 |
CVE-2019-25602 | 3.5 | 5.5 | 0.0011 | 2026-03-22 |
CVE-2018-25238 | 3.5 | 6.2 | 0.0016 | 2026-04-04 |
CVE-2018-25240 | 3.5 | 6.2 | 0.0012 | 2026-04-04 |