CVE-2023-54228
Unknown Unknown - Not Provided
Resource Leak in Linux Kernel Clock Regulator Fixed

Publication date: 2025-12-30

Last updated on: 2025-12-30

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: regulator: raa215300: Fix resource leak in case of error The clk_register_clkdev() allocates memory by calling vclkdev_alloc() and this memory is not freed in the error path. Similarly, resources allocated by clk_register_fixed_rate() are not freed in the error path. Fix these issues by using devm_clk_hw_register_fixed_rate() and devm_clk_hw_register_clkdev(). After this, the static variable clk is not needed. Replace it withΒ  local variable hw in probe() and drop calling clk_unregister_fixed_rate() from raa215300_rtc_unregister_device().
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-30
Last Modified
2025-12-30
Generated
2026-05-07
AI Q&A
2025-12-30
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
What immediate steps should I take to mitigate this vulnerability?

To mitigate this vulnerability, update the Linux kernel to a version that includes the fix for the resource leak in the regulator raa215300 driver. The fix involves using devm_clk_hw_register_fixed_rate() and devm_clk_hw_register_clkdev() to properly manage memory allocation and avoid leaks. Avoid using vulnerable kernel versions that do not include these changes.


Can you explain this vulnerability to me?

This vulnerability in the Linux kernel involves a resource leak caused by memory allocated during clock device registration not being freed properly in error paths. Specifically, memory allocated by clk_register_clkdev() and clk_register_fixed_rate() is not released if an error occurs. The fix involves using devm_clk_hw_register_fixed_rate() and devm_clk_hw_register_clkdev() to ensure proper resource management and replacing a static variable with a local variable to avoid unnecessary unregister calls.


How can this vulnerability impact me? :

The impact of this vulnerability is a resource leak in the Linux kernel, which could lead to increased memory usage and potentially degrade system stability or performance over time if errors occur during clock device registration.


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