Linux: Out-of-bounds Read
CVE-2025-38027 is a high-severity out-of-bounds read vulnerability in Linux, with a CVSS 3.1 base score of 7.1 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 6ba30f7aa2c550b2ac04f16b81a19a8c045b8660, 7bddac8603d4e396872c2fbf4403ec08e7b1d7c8, d2a9a92bb4cc7568cff68241b0051dc7268bdc68 as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.21% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Linux to 6ba30f7aa2c550b2ac04f16b81a19a8c045b8660 or 7bddac8603d4e396872c2fbf4403ec08e7b1d7c8 or d2a9a92bb4cc7568cff68241b0051dc7268bdc68 or 5578ab04bd7732f470fc614bbc0a924900399fb8, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.1.140 or 6.6.92 or 6.12.30 or 6.14.8, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | bfff546aae50ae68ed395bf0e0848188d27b0ba3 up to, but not including, 6ba30f7aa2c550b2ac04f16b81a19a8c045b8660; bfff546aae50ae68ed395bf0e0848188d27b0ba3 up to, but not including, 7bddac8603d4e396872c2fbf4403ec08e7b1d7c8; bfff546aae50ae68ed395bf0e0848188d27b0ba3 up to, but not including, d2a9a92bb4cc7568cff68241b0051dc7268bdc68; bfff546aae50ae68ed395bf0e0848188d27b0ba3 up to, but not including, 5578ab04bd7732f470fc614bbc0a924900399fb8; bfff546aae50ae68ed395bf0e0848188d27b0ba3 up to, but not including, 6b0cd72757c69bc2d45da42b41023e288d02e772; 5.17 | 6ba30f7aa2c550b2ac04f16b81a19a8c045b8660, 7bddac8603d4e396872c2fbf4403ec08e7b1d7c8, d2a9a92bb4cc7568cff68241b0051dc7268bdc68, 5578ab04bd7732f470fc614bbc0a924900399fb8, 6b0cd72757c69bc2d45da42b41023e288d02e772 |
| Linux | Linux Kernel | 5.17 up to, but not including, 6.1.140; 6.2 up to, but not including, 6.6.92; 6.7 up to, but not including, 6.12.30; 6.13 up to, but not including, 6.14.8; 6.15 | 6.1.140, 6.6.92, 6.12.30, 6.14.8 |
| Debian | Debian Linux | 11.0 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H. Scored by NVD.
Official description
In the Linux kernel, the following vulnerability has been resolved: regulator: max20086: fix invalid memory access max20086_parse_regulators_dt() calls of_regulator_match() using an array of struct of_regulator_match allocated on the stack for the matches argument. of_regulator_match() calls devm_of_regulator_put_matches(), which calls devres_alloc() to allocate a struct devm_of_regulator_matches which will be de-allocated using devm_of_regulator_put_matches(). struct devm_of_regulator_matches is populated with the stack allocated matches array. If the device fails to probe, devm_of_regulator_put_matches() will be called and will try to call of_node_put() on that stack pointer, generating the following dmesg entries: max20086 6-0028: Failed to read DEVICE_ID reg: -121 kobject: '\xc0$\xa5\x03' (000000002cebcb7a): is not initialized, yet kobject_put() is being called. Followed by a stack trace matching the call flow described above. Switch to allocating the matches array using devm_kcalloc() to avoid accessing the stack pointer long after it's out of scope. This also has the advantage of allowing multiple max20086 to probe without overriding the data stored inside the global of_regulator_match.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Out-of-bounds Read
The product reads data past the end, or before the beginning, of the intended buffer.
How developers prevent this class of flaw
- Use a language that provides appropriate memory abstractions.
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- git.kernel.org/stable/c/5578ab04bd7732f470fc614bbc0a924900399fb8
- git.kernel.org/stable/c/6b0cd72757c69bc2d45da42b41023e288d02e772
- git.kernel.org/stable/c/6ba30f7aa2c550b2ac04f16b81a19a8c045b8660
- git.kernel.org/stable/c/7bddac8603d4e396872c2fbf4403ec08e7b1d7c8
- git.kernel.org/stable/c/d2a9a92bb4cc7568cff68241b0051dc7268bdc68
Third-party and government advisories
- lists.debian.org/debian-lts-announce/2025/08/msg00010.htmlThird Party Advisory
Recent Out-of-bounds Read vulnerabilities
- 7.5 High severity
- 7.1 High severity
- 7.1 High severity
- 7.1 High severity
- 7.1 High severity
- 7.1 High severity
Spotted an error? Tell us.