CVE-2023-54101
Unknown Unknown - Not Provided
Use-After-Free in Linux soc:xilinx Driver Causes Memory Corruption

Publication date: 2025-12-24

Last updated on: 2025-12-24

Assigner: kernel.org

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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-24
Last Modified
2025-12-24
Generated
2026-05-07
AI Q&A
2025-12-24
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
xilinx soc *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability is a use-after-free issue in the Linux kernel's Xilinx SoC driver. Specifically, the code uses a loop iterator (hash_for_each_possible) that dereferences a pointer (eve_data) to get the next item in a list, but the loop frees eve_data during iteration, leading to use-after-free. The fix involves using a safer loop iterator (hash_for_each_possible_safe) to avoid accessing freed memory.


How can this vulnerability impact me? :

A 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. In this case, it could compromise the stability and security of systems running the affected Linux kernel with the Xilinx SoC driver.


What immediate steps should I take to mitigate this vulnerability?

Update the Linux kernel to a version where the vulnerability is fixed by replacing the use of hash_for_each_possible() with hash_for_each_possible_safe() in the xilinx soc driver to avoid use after free. This involves applying the patch that uses a safe loop iterator in the driver code.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart