Linux: Out-of-bounds Write
CVE-2025-38484 is a high-severity out-of-bounds write vulnerability in Linux, with a CVSS 3.1 base score of 7.8 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 6eea9f7648ddb9e4903735a1f77cf196c957aa38, 01e941aa7f5175125df4ac5d3aab099961525602, da9374819eb3885636934c1006d450c3cb1a02ed 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.17% 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 6eea9f7648ddb9e4903735a1f77cf196c957aa38 or 01e941aa7f5175125df4ac5d3aab099961525602 or da9374819eb3885636934c1006d450c3cb1a02ed or 6.12.40, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.12.40 or 6.14 or 6.15.8, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | df3892e5e861c43d5612728ed259634675b8a71f up to, but not including, 6eea9f7648ddb9e4903735a1f77cf196c957aa38; 035b4989211dc1c8626e186d655ae8ca5141bb73 up to, but not including, 01e941aa7f5175125df4ac5d3aab099961525602; 035b4989211dc1c8626e186d655ae8ca5141bb73 up to, but not including, da9374819eb3885636934c1006d450c3cb1a02ed; 04271a4d2740f98bbe36f82cd3d74677a839d1eb; fd791c81f410ab1c554686a6f486dc7a176dfe35; 6.12.23 up to, but not including, 6.12.40; 6.13.11 up to, but not including, 6.14; 6.14.2 up to, but not including, 6.15; and 1 more ranges | 6eea9f7648ddb9e4903735a1f77cf196c957aa38, 01e941aa7f5175125df4ac5d3aab099961525602, da9374819eb3885636934c1006d450c3cb1a02ed, 6.12.40, 6.14, 6.15 |
| Linux | Linux Kernel | 6.12.23 up to, but not including, 6.12.40; 6.13.11 up to, but not including, 6.14; 6.14.2 up to, but not including, 6.15.8; 6.16 | 6.12.40, 6.14, 6.15.8 |
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
- HighData or code can be modified at will.
- 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:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.8 | High | CNA |
| CVSS 3.1 | 7.8 | High | NVD |
Official description
In the Linux kernel, the following vulnerability has been resolved: iio: backend: fix out-of-bound write The buffer is set to 80 character. If a caller write more characters, count is truncated to the max available space in "simple_write_to_buffer". But afterwards a string terminator is written to the buffer at offset count without boundary check. The zero termination is written OUT-OF-BOUND. Add a check that the given buffer is smaller then the buffer to prevent.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Out-of-bounds Write
The product writes data past the end, or before the beginning, of the intended buffer.
How developers prevent this class of flaw
- Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Recent Out-of-bounds Write vulnerabilities
- 7.5 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
- 7.8 High severity
- 9.8 Critical severity
Spotted an error? Tell us.