CyberSecBulletin
CVE-2025-37927NVD status: Analyzed

Linux: Out-of-bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2025-37927 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 2b65060c84ee4d8dc64fae6d2728b528e9e832e1, a65ebfed65fa62797ec1f5f1dcf7adb157a2de1e, 466d9da267079a8d3b69fa72dfa3a732e1f6dbb5 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.29% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Linux to 2b65060c84ee4d8dc64fae6d2728b528e9e832e1 or a65ebfed65fa62797ec1f5f1dcf7adb157a2de1e or 466d9da267079a8d3b69fa72dfa3a732e1f6dbb5 or c3f37faa71f5d26dd2144b3f2b14525ec8f5e41f, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 5.4.294 or 5.10.238 or 5.15.182 or 6.1.138, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxca3bf5d47cec8b7614bcb2e9132c40081d6d81db up to, but not including, 2b65060c84ee4d8dc64fae6d2728b528e9e832e1; ca3bf5d47cec8b7614bcb2e9132c40081d6d81db up to, but not including, a65ebfed65fa62797ec1f5f1dcf7adb157a2de1e; ca3bf5d47cec8b7614bcb2e9132c40081d6d81db up to, but not including, 466d9da267079a8d3b69fa72dfa3a732e1f6dbb5; ca3bf5d47cec8b7614bcb2e9132c40081d6d81db up to, but not including, c3f37faa71f5d26dd2144b3f2b14525ec8f5e41f; ca3bf5d47cec8b7614bcb2e9132c40081d6d81db up to, but not including, 13d67528e1ae4486e9ab24b70122fab104c73c29; ca3bf5d47cec8b7614bcb2e9132c40081d6d81db up to, but not including, 10d901a95f8e766e5aa0bb9a983fb41271f64718; ca3bf5d47cec8b7614bcb2e9132c40081d6d81db up to, but not including, c8bdfc0297965bb13fa439d36ca9c4f7c8447f0f; ca3bf5d47cec8b7614bcb2e9132c40081d6d81db up to, but not including, 8dee308e4c01dea48fc104d37f92d5b58c50b96c; and 1 more ranges2b65060c84ee4d8dc64fae6d2728b528e9e832e1, a65ebfed65fa62797ec1f5f1dcf7adb157a2de1e, 466d9da267079a8d3b69fa72dfa3a732e1f6dbb5, c3f37faa71f5d26dd2144b3f2b14525ec8f5e41f, 13d67528e1ae4486e9ab24b70122fab104c73c29, 10d901a95f8e766e5aa0bb9a983fb41271f64718
LinuxLinux Kernel4.7 up to, but not including, 5.4.294; 5.5 up to, but not including, 5.10.238; 5.11 up to, but not including, 5.15.182; 5.16 up to, but not including, 6.1.138; 6.2 up to, but not including, 6.6.90; 6.7 up to, but not including, 6.12.28; 6.13 up to, but not including, 6.14.6; 6.155.4.294, 5.10.238, 5.15.182, 6.1.138, 6.6.90, 6.12.28
DebianDebian Linux11.0Not 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
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: iommu/amd: Fix potential buffer overflow in parse_ivrs_acpihid There is a string parsing logic error which can lead to an overflow of hid or uid buffers. Comparing ACPIID_LEN against a total string length doesn't take into account the lengths of individual hid and uid buffers so the check is insufficient in some cases. For example if the length of hid string is 4 and the length of the uid string is 260, the length of str will be equal to ACPIID_LEN + 1 but uid string will overflow uid buffer which size is 256. The same applies to the hid string with length 13 and uid string with length 250. Check the length of hid and uid strings separately to prevent buffer overflow. Found by Linux Verification Center (linuxtesting.org) with SVACE.

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.

More Out-of-bounds Write vulnerabilities (CWE-787)

Timeline

  1. CVE record published.
  2. Record last changed materially (score, affected products, status or references).

References

Third-party and government advisories

Recent Out-of-bounds Write vulnerabilities

Spotted an error? Tell us.