CVE-2025-38027
BaseFortify
Publication date: 2025-06-18
Last updated on: 2025-12-18
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 5.17 (inc) to 6.1.140 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.6.92 (exc) |
| linux | linux_kernel | From 6.7 (inc) to 6.12.30 (exc) |
| linux | linux_kernel | From 6.13 (inc) to 6.14.8 (exc) |
| linux | linux_kernel | 6.15 |
| linux | linux_kernel | 6.15 |
| linux | linux_kernel | 6.15 |
| linux | linux_kernel | 6.15 |
| linux | linux_kernel | 6.15 |
| linux | linux_kernel | 6.15 |
| debian | debian_linux | 11.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-125 | The product reads data past the end, or before the beginning, of the intended buffer. |
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 where the matches array is allocated using devm_kcalloc() instead of on the stack. This prevents invalid memory access and related errors. If updating is not immediately possible, monitor system logs for the described errors and avoid using affected max20086 devices until patched.
Can you explain this vulnerability to me?
This vulnerability involves the Linux kernel's max20086 regulator driver improperly handling memory allocation. Specifically, the function max20086_parse_regulators_dt() uses an array allocated on the stack as an argument to of_regulator_match(). Later, when the device fails to probe, a cleanup function tries to free or access this stack-allocated memory, which is no longer valid. This leads to invalid memory access and error messages in the system logs, potentially causing instability or crashes. The fix was to allocate this array dynamically using devm_kcalloc(), ensuring the memory remains valid during cleanup.
How can this vulnerability impact me? :
This vulnerability can cause invalid memory access in the Linux kernel when probing the max20086 device regulator. This may result in kernel error messages, instability, or crashes related to device initialization failures. It could affect system reliability and potentially lead to denial of service conditions if the device cannot be properly initialized or cleaned up.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking the system logs (dmesg) for specific error messages related to the max20086 regulator driver. Look for entries such as 'max20086 6-0028: Failed to read DEVICE_ID reg: -121' and 'kobject: ... is not initialized, yet kobject_put() is being called.' You can use the command 'dmesg | grep max20086' or 'dmesg | grep kobject' to find these messages.