BaseFortify

Publication date: 2025-10-04

Last updated on: 2026-03-21

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: clk: imx: scu: use _safe list iterator to avoid a use after free This loop is freeing "clk" so it needs to use list_for_each_entry_safe(). Otherwise it dereferences a freed variable to get the next item on the loop.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2025-10-04

Last Modified

2026-03-21

Generated

2026-07-06

AI Q&A

2025-10-04

EPSS Evaluated

2026-07-05

NVD

CVE-2023-53572

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	From 5.16 (inc) to 6.1.39 (inc)
linux	kernel	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-416	The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

Attack-Flow Graph

Executive Summary

This vulnerability in the Linux kernel involves improper handling of a list iteration in the clk: imx: scu component. The code was freeing a 'clk' object inside a loop but did not use a safe list iterator, leading to a use-after-free condition where the code dereferences a freed variable to get the next item in the loop. The fix involved using a safe list iterator (list_for_each_entry_safe) to avoid this issue.

Impact Analysis

The use-after-free vulnerability can lead to undefined behavior such as system crashes, data corruption, or potential exploitation by attackers to execute arbitrary code or escalate privileges within the Linux kernel environment.

Hi! I’m here to help you understand CVE-2023-53572. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70