VYPR
Unrated severityNVD Advisory· Published Dec 24, 2025· Updated Apr 15, 2026

CVE-2023-54101

CVE-2023-54101

Description

In the Linux kernel, the following vulnerability has been resolved:

driver: soc: xilinx: use _safe loop iterator to avoid a use after free

The hash_for_each_possible() loop dereferences "eve_data" to get the next item on the list. However the loop frees eve_data so it leads to a use after free. Use hash_for_each_possible_safe() instead.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

A use-after-free in the Linux kernel's Xilinx driver occurs when hash_for_each_possible() dereferences freed memory; fixed with _safe iterator.

Vulnerability

In the Linux kernel's Xilinx soc driver, a use-after-free vulnerability exists in code using the hash_for_each_possible() macro. The loop dereferences eve_data to obtain the next list item, but eve_data can be freed inside the loop. This leads to a use-after-free condition if the freed memory is accessed.

Exploitation

An attacker with local access and the ability to trigger the vulnerable code path could exploit this bug. The attack surface is limited to systems using the Xilinx driver, but no special privileges beyond local user access are required to trigger the loop.

Impact

Successful exploitation could allow an attacker to cause a kernel crash (denial of service) or potentially escalate privileges, as use-after-free bugs in kernel drivers are often exploitable for arbitrary code execution.

Mitigation

The fix is to use the safe iterator hash_for_each_possible_safe(), which ensures proper handling when elements are freed during traversal. This commit is included in upstream Linux kernels; users should apply the patch or update to a kernel version containing the fix [1].

AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

1

Patches

4

Vulnerability mechanics

Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.

References

4

News mentions

0

No linked articles in our index yet.