Invalid memory access via stale stack pointer
Published Jun 18, 2025 · Updated May 11, 2026
Memory lifetime error in the Linux max20086 regulator driver from 5.17 allows local users to trigger invalid memory access during probe cleanup. max20086_parse_regulators_dt() places the regulator-match array on the stack, while device-managed cleanup retains that pointer and later passes it to of_node_put() after the array is out of scope. Reachability requires a MAX20086 device probe to fail; the documented result is invalid cleanup access with kernel diagnostics, while further consequences are not established.
Summary
What happened
Memory lifetime error in the Linux max20086 regulator driver from 5.17 allows local users to trigger invalid memory access during probe cleanup. max20086_parse_regulators_dt() places the regulator-match array on the stack, while device-managed cleanup retains that pointer and later passes it to of_node_put() after the array is out of scope. Reachability requires a MAX20086 device probe to fail; the documented result is invalid cleanup access with kernel diagnostics, while further consequences are not established.
The record
- CVE
- CVE-2025-38027
- Published
- Jun 18, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-125
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 18, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.17
- Affected versionversion=bfff546aae50ae68ed395bf0e0848188d27b0ba3 <5578ab04bd7732f470fc614bbc0a924900399fb8
- Affected versionversion=bfff546aae50ae68ed395bf0e0848188d27b0ba3 <6b0cd72757c69bc2d45da42b41023e288d02e772
- Affected versionversion=bfff546aae50ae68ed395bf0e0848188d27b0ba3 <6ba30f7aa2c550b2ac04f16b81a19a8c045b8660
- Affected versionversion=bfff546aae50ae68ed395bf0e0848188d27b0ba3 <7bddac8603d4e396872c2fbf4403ec08e7b1d7c8
- Affected versionversion=bfff546aae50ae68ed395bf0e0848188d27b0ba3 <d2a9a92bb4cc7568cff68241b0051dc7268bdc68
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo