Linux: Out-of-bounds Write
CVE-2025-38585 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 51b8dc5163d2ff2bf04019f8bf7e3bd0e75bb654, 3d672fe065aa00f4d66f42e3c9720f69a3ed43e7, e6d3453a002e89537e6136f6c774659b297a549b 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.25% 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 51b8dc5163d2ff2bf04019f8bf7e3bd0e75bb654 or 3d672fe065aa00f4d66f42e3c9720f69a3ed43e7 or e6d3453a002e89537e6136f6c774659b297a549b or 1a7a2f59fb2eb0718a0cff1e5822500cefe50ed9, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.12.42 or 6.15.10 or 6.16.1, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | a49d25364dfb9f8a64037488a39ab1f56c5fa419 up to, but not including, 51b8dc5163d2ff2bf04019f8bf7e3bd0e75bb654; ad85094b293e40e7a2f831b0311a389d952ebd5e up to, but not including, 3d672fe065aa00f4d66f42e3c9720f69a3ed43e7; ad85094b293e40e7a2f831b0311a389d952ebd5e up to, but not including, e6d3453a002e89537e6136f6c774659b297a549b; ad85094b293e40e7a2f831b0311a389d952ebd5e up to, but not including, 1a7a2f59fb2eb0718a0cff1e5822500cefe50ed9; ad85094b293e40e7a2f831b0311a389d952ebd5e up to, but not including, ee4cf798202d285dcbe85e4467a094c44f5ed8e6; 4.12; 5.8 | 51b8dc5163d2ff2bf04019f8bf7e3bd0e75bb654, 3d672fe065aa00f4d66f42e3c9720f69a3ed43e7, e6d3453a002e89537e6136f6c774659b297a549b, 1a7a2f59fb2eb0718a0cff1e5822500cefe50ed9, ee4cf798202d285dcbe85e4467a094c44f5ed8e6 |
| Linux | Linux Kernel | 6.0 up to, but not including, 6.12.42; 6.13 up to, but not including, 6.15.10; 6.16 up to, but not including, 6.16.1 | 6.12.42, 6.15.10, 6.16.1 |
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.
Official description
In the Linux kernel, the following vulnerability has been resolved: staging: media: atomisp: Fix stack buffer overflow in gmin_get_var_int() When gmin_get_config_var() calls efi.get_variable() and the EFI variable is larger than the expected buffer size, two behaviors combine to create a stack buffer overflow: 1. gmin_get_config_var() does not return the proper error code when efi.get_variable() fails. It returns the stale 'ret' value from earlier operations instead of indicating the EFI failure. 2. When efi.get_variable() returns EFI_BUFFER_TOO_SMALL, it updates *out_len to the required buffer size but writes no data to the output buffer. However, due to bug #1, gmin_get_var_int() believes the call succeeded. The caller gmin_get_var_int() then performs: - Allocates val[CFG_VAR_NAME_MAX + 1] (65 bytes) on stack - Calls gmin_get_config_var(dev, is_gmin, var, val, &len) with len=64 - If EFI variable is >64 bytes, efi.get_variable() sets len=required_size - Due to bug #1, thinks call succeeded with len=required_size - Executes val[len] = 0, writing past end of 65-byte stack buffer This creates a stack buffer overflow when EFI variables are larger than 64 bytes. Since EFI variables can be controlled by firmware or system configuration, this could potentially be exploited for code execution. Fix the bug by returning proper error codes from gmin_get_config_var() based on EFI status instead of stale 'ret' value. The gmin_get_var_int() function is called during device initialization for camera sensor configuration on Intel Bay Trail and Cherry Trail platforms using the atomisp camera stack.
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
Other references
Recent Out-of-bounds Write vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 8.1 High severity
- 9.8 Critical severity
- 7.8 High severity
Spotted an error? Tell us.