CWE · MITRE source
CWE-825Expired Pointer Dereference
The product dereferences a pointer that contains a location for memory that was previously valid, but is no longer valid.
When a product releases memory, but it maintains a pointer to that memory, then the memory might be re-allocated at a later time. If the original pointer is accessed to read or write data, then this could cause the product to read or modify data that is in use by a different function or process. Depending on how the newly-allocated memory is used, this could lead to a denial of service, information exposure, or code execution.
Last updated: 04 July 2026 00:28 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 · 5 mapping(s) from 1 framework(s): ATT&CK 5 (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-23638 UPD | 8.0 | 6.5 | 0.6005 | 2024-01-24 |
CVE-2023-48316 | 7.0 | 9.8 | 0.0433 | 2023-12-05 |
CVE-2023-48692 | 7.0 | 9.0 | 0.0313 | 2023-12-05 |
CVE-2024-23310 UPD | 7.0 | 9.8 | 0.0170 | 2024-02-20 |
CVE-2025-49794 UPD | 7.0 | 9.1 | 0.0067 | 2025-06-16 |
CVE-2026-4688 UPD | 7.0 | 10.0 | 0.0053 | 2026-03-24 |
CVE-2026-4691 UPD | 7.0 | 9.8 | 0.0048 | 2026-03-24 |
CVE-2026-4696 UPD | 7.0 | 9.8 | 0.0048 | 2026-03-24 |
CVE-2026-4721 UPD | 7.0 | 9.8 | 0.0042 | 2026-03-24 |
CVE-2026-4729 UPD | 7.0 | 9.8 | 0.0033 | 2026-03-24 |
CVE-2026-6722 UPD | 7.0 | 9.8 | 0.0074 | 2026-05-10 |
CVE-2026-45972 UPD | 7.0 | 9.8 | 0.0033 | 2026-05-27 |
CVE-2026-12293 UPD | 7.0 | 9.8 | 0.0030 | 2026-06-16 |
CVE-2026-52924 | 7.0 | 9.8 | 0.0027 | 2026-06-24 |
CVE-2026-53006 | 7.0 | 9.8 | 0.0038 | 2026-06-24 |
CVE-2019-15691 | 5.5 | 7.2 | 0.0472 | 2019-12-26 |
CVE-2023-20212 | 5.5 | 7.5 | 0.0260 | 2023-08-18 |
CVE-2023-48315 | 5.5 | 8.8 | 0.0390 | 2023-12-05 |
CVE-2024-39792 | 5.5 | 7.5 | 0.0063 | 2024-08-14 |
CVE-2024-8250 | 5.5 | 7.8 | 0.0032 | 2024-08-29 |
CVE-2025-49795 UPD | 5.5 | 7.5 | 0.0047 | 2025-06-16 |
CVE-2026-23074 UPD | 5.5 | 7.8 | 0.0013 | 2026-02-04 |
CVE-2026-24678 UPD | 5.5 | 7.5 | 0.0063 | 2026-02-09 |
CVE-2026-30978 | 5.5 | 7.8 | 0.0026 | 2026-03-10 |
CVE-2026-32873 | 5.5 | 7.5 | 0.0060 | 2026-03-20 |