CVE-2025-39830
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-09-16

Last updated on: 2025-12-02

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: net/mlx5: HWS, Fix memory leak in hws_pool_buddy_init error path In the error path of hws_pool_buddy_init(), the buddy allocator cleanup doesn't free the allocator structure itself, causing a memory leak. Add the missing kfree() to properly release all allocated memory.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-09-16
Last Modified
2025-12-02
Generated
2026-05-07
AI Q&A
2025-09-16
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 4 associated CPEs
Vendor Product Version / Range
linux linux_kernel From 6.12 (inc) to 6.16.5 (exc)
linux linux_kernel 6.17
linux linux_kernel 6.17
linux linux_kernel 6.17
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 Powered Q&A
Can you explain this vulnerability to me?

This vulnerability is a memory leak in the Linux kernel's net/mlx5 subsystem. Specifically, in the error path of the function hws_pool_buddy_init(), the buddy allocator cleanup process does not free the allocator structure itself, which causes allocated memory to not be released properly. The fix involves adding the missing kfree() call to ensure all allocated memory is freed.


How can this vulnerability impact me? :

This memory leak can lead to increased memory usage over time, potentially causing system instability or degraded performance if the leaked memory accumulates. It may affect systems running the affected Linux kernel version, especially those using the net/mlx5 subsystem.


What immediate steps should I take to mitigate this vulnerability?

Apply the updated Linux kernel patch that fixes the memory leak in the hws_pool_buddy_init error path by adding the missing kfree() call to properly release allocated memory.


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