CVE-2023-53267
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-09-16

Last updated on: 2025-12-03

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: driver: soc: xilinx: fix memory leak in xlnx_add_cb_for_notify_event() The kfree() should be called when memory fails to be allocated for cb_data in xlnx_add_cb_for_notify_event(), otherwise there will be a memory leak, so add kfree() to fix it.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-09-16
Last Modified
2025-12-03
Generated
2026-06-16
AI Q&A
2025-09-16
EPSS Evaluated
2026-06-15
NVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
linux linux_kernel From 5.19 (inc) to 6.1.18 (exc)
linux linux_kernel From 6.2 (inc) to 6.2.5 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-401 The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability is a memory leak in the Linux kernel's Xilinx SoC driver. Specifically, when memory allocation for cb_data in the function xlnx_add_cb_for_notify_event() fails, the allocated memory is not freed properly, causing a memory leak. The fix involves adding a call to kfree() to release the memory when allocation fails.

Impact Analysis

The memory leak caused by this vulnerability can lead to increased memory usage over time, potentially degrading system performance or causing the system to run out of memory, which may result in crashes or instability.

Mitigation Strategies

Apply the patch or update to the Linux kernel version that includes the fix for the memory leak in the xilinx soc driver, specifically the fix in xlnx_add_cb_for_notify_event() where kfree() is called properly to prevent the leak.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2023-53267. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart