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: 15 October 2026 14:21 UTC
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
NIST 800-53 r5 controls PROPOSED for this weakness (0)AI-assisted
These are model PROPOSALS, not graded mappings. They come
from controls_to_cwe_proposals, which carries no grade field at
all; across the CWE pages 1,540 of 1,722 such associations (89%) have never
been graded by anything. The heading said “address” until
2026-09-29, which asserted a relationship the data does not carry.
Graded cross-walks are on the framework map, not here.
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
| No NIST controls proposed yet. | |||
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2024-4778 UPD | 7.3 | 9.8 | 0.0044 | 2024-05-14 |
CVE-2019-1164 UPD | 6.0 | 7.8 | 0.0094 | 2019-08-14 |
CVE-2025-1937 UPD | 5.8 | 7.5 | 0.0056 | 2025-03-04 |
CVE-2022-27813 UPD | 5.6 | 8.1 | 0.0019 | 2023-10-19 |
CVE-2025-22889 UPD | 5.4 | 7.9 | 0.0015 | 2025-08-12 |
CVE-2019-25585 | 4.7 | 6.2 | 0.0018 | 2026-03-22 |
CVE-2019-25592 UPD | 4.7 | 6.2 | 0.0016 | 2026-03-22 |
CVE-2018-25238 UPD | 4.7 | 6.2 | 0.0016 | 2026-04-04 |
CVE-2019-25572 UPD | 4.6 | 6.2 | 0.0016 | 2026-03-21 |
CVE-2018-25240 UPD | 4.6 | 6.2 | 0.0012 | 2026-04-04 |
CVE-2026-76668 | 4.5 | 6.3 | 0.0008 | 2026-10-15 |
CVE-2019-25559 UPD | 4.2 | 5.5 | 0.0017 | 2026-03-21 |
CVE-2019-25570 | 4.2 | 5.5 | 0.0022 | 2026-03-21 |
CVE-2019-25602 UPD | 4.1 | 5.5 | 0.0011 | 2026-03-22 |
CVE-2025-31936 UPD | 4.1 | 5.7 | 0.0010 | 2026-08-11 |