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: 15 October 2026 07:26 UTC
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
ID.RA-01ID.AM-08PR.PS-02PR.PS-06
—
—
—
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-2023-48316 UPD | 7.9 | 9.8 | 0.0433 | 2023-12-05 |
CVE-2024-23310 UPD | 7.6 | 9.8 | 0.0170 | 2024-02-20 |
CVE-2026-6722 UPD | 7.6 | 9.8 | 0.0129 | 2026-05-10 |
CVE-2024-23638 UPD | 7.4 | 6.5 | 0.6005 | 2024-01-24 |
CVE-2026-4688 UPD | 7.4 | 10.0 | 0.0053 | 2026-03-24 |
CVE-2026-4691 UPD | 7.3 | 9.8 | 0.0048 | 2026-03-24 |
CVE-2026-4696 UPD | 7.3 | 9.8 | 0.0048 | 2026-03-24 |
CVE-2026-4721 UPD | 7.3 | 9.8 | 0.0042 | 2026-03-24 |
CVE-2026-4729 UPD | 7.3 | 9.8 | 0.0046 | 2026-03-24 |
CVE-2026-52924 UPD | 7.3 | 9.8 | 0.0053 | 2026-06-24 |
CVE-2026-53006 UPD | 7.3 | 9.8 | 0.0039 | 2026-06-24 |
CVE-2026-45972 UPD | 7.2 | 9.8 | 0.0033 | 2026-05-27 |
CVE-2026-12293 UPD | 7.2 | 9.8 | 0.0030 | 2026-06-16 |
CVE-2026-53175 UPD | 7.2 | 9.8 | 0.0031 | 2026-06-25 |
CVE-2023-48315 UPD | 7.1 | 8.8 | 0.0390 | 2023-12-05 |
CVE-2026-45447 UPD | 7.1 | 8.8 | 0.0400 | 2026-06-09 |
CVE-2025-49794 UPD | 7.0 | 9.1 | 0.0083 | 2025-06-16 |
CVE-2023-48692 UPD | 6.8 | 9.0 | 0.0311 | 2023-12-05 |
CVE-2026-33526 UPD | 6.7 | 7.5 | 0.0894 | 2026-03-26 |
CVE-2026-46125 UPD | 6.5 | 8.8 | 0.0044 | 2026-05-28 |
CVE-2026-12291 UPD | 6.5 | 8.8 | 0.0038 | 2026-06-16 |
CVE-2023-20212 UPD | 6.4 | 7.5 | 0.0344 | 2023-08-18 |
CVE-2026-46166 UPD | 6.4 | 8.8 | 0.0029 | 2026-05-28 |
CVE-2026-34774 UPD | 6.2 | 8.1 | 0.0055 | 2026-04-04 |
CVE-2026-6100 UPD | 6.2 | 8.1 | 0.0076 | 2026-04-13 |