CyberSecBulletin
CVE-2025-37979NVD status: Modified

Linux: Out-of-bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2025-37979 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 d78888853eb53f47ae16cf3aa5d0444d0331b9f8, a12c14577882b1f2b4cff0f86265682f16e97b0c, c0ce01e0ff8a0d61a7b089ab309cdc12bc527c39 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.22% 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 d78888853eb53f47ae16cf3aa5d0444d0331b9f8 or a12c14577882b1f2b4cff0f86265682f16e97b0c or c0ce01e0ff8a0d61a7b089ab309cdc12bc527c39 or b807b7c81a6d066757a94af7b8fa5b6a37e4d0b3, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 6.1.136 or 6.6.88 or 6.12.25 or 6.14.4, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux77d0ffef793da818741127f4905a3e3d45d05ac7 up to, but not including, d78888853eb53f47ae16cf3aa5d0444d0331b9f8; 77d0ffef793da818741127f4905a3e3d45d05ac7 up to, but not including, a12c14577882b1f2b4cff0f86265682f16e97b0c; 77d0ffef793da818741127f4905a3e3d45d05ac7 up to, but not including, c0ce01e0ff8a0d61a7b089ab309cdc12bc527c39; 77d0ffef793da818741127f4905a3e3d45d05ac7 up to, but not including, b807b7c81a6d066757a94af7b8fa5b6a37e4d0b3; 77d0ffef793da818741127f4905a3e3d45d05ac7 up to, but not including, a31a4934b31faea76e735bab17e63d02fcd8e029; 5.18d78888853eb53f47ae16cf3aa5d0444d0331b9f8, a12c14577882b1f2b4cff0f86265682f16e97b0c, c0ce01e0ff8a0d61a7b089ab309cdc12bc527c39, b807b7c81a6d066757a94af7b8fa5b6a37e4d0b3, a31a4934b31faea76e735bab17e63d02fcd8e029
LinuxLinux Kernel5.18 up to, but not including, 6.1.136; 6.2 up to, but not including, 6.6.88; 6.7 up to, but not including, 6.12.25; 6.13 up to, but not including, 6.14.4; 6.156.1.136, 6.6.88, 6.12.25, 6.14.4
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.

Scoring systemScoreSeverityScored by
CVSS 3.17.8HighCNA
CVSS 3.17.8HighNVD

Official description

In the Linux kernel, the following vulnerability has been resolved: ASoC: qcom: Fix sc7280 lpass potential buffer overflow Case values introduced in commit 5f78e1fb7a3e ("ASoC: qcom: Add driver support for audioreach solution") cause out of bounds access in arrays of sc7280 driver data (e.g. in case of RX_CODEC_DMA_RX_0 in sc7280_snd_hw_params()). Redefine LPASS_MAX_PORTS to consider the maximum possible port id for q6dsp as sc7280 driver utilizes some of those values. 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.