CyberSecBulletin
CVE-2025-37810NVD status: Analyzed

Linux: Out-of-bounds Write

CVE-2025-37810 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 015c39f38e69a491d2abd5e98869a500a9459b3b, b43225948b231b3f331194010f84512bee4d9f59, c0079630f268843a25ed75226169cba40e0d8880 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.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Linux to 015c39f38e69a491d2abd5e98869a500a9459b3b or b43225948b231b3f331194010f84512bee4d9f59 or c0079630f268843a25ed75226169cba40e0d8880 or a44547015287a19001384fe94dbff84c92ce4ee1, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 5.4.293 or 5.10.237 or 5.15.181 or 6.1.136, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux72246da40f3719af3bfd104a2365b32537c27d83 up to, but not including, 015c39f38e69a491d2abd5e98869a500a9459b3b; 72246da40f3719af3bfd104a2365b32537c27d83 up to, but not including, b43225948b231b3f331194010f84512bee4d9f59; 72246da40f3719af3bfd104a2365b32537c27d83 up to, but not including, c0079630f268843a25ed75226169cba40e0d8880; 72246da40f3719af3bfd104a2365b32537c27d83 up to, but not including, a44547015287a19001384fe94dbff84c92ce4ee1; 72246da40f3719af3bfd104a2365b32537c27d83 up to, but not including, c4d80e41cb42008dceb35e5dbf52574d93beac0d; 72246da40f3719af3bfd104a2365b32537c27d83 up to, but not including, 52a7c9d930b95aa8b1620edaba4818040c32631f; 72246da40f3719af3bfd104a2365b32537c27d83 up to, but not including, 99d655119b870ee60e4dbf310aa9a1ed8d9ede3d; 72246da40f3719af3bfd104a2365b32537c27d83 up to, but not including, 63ccd26cd1f6600421795f6ca3e625076be06c9f; and 1 more ranges015c39f38e69a491d2abd5e98869a500a9459b3b, b43225948b231b3f331194010f84512bee4d9f59, c0079630f268843a25ed75226169cba40e0d8880, a44547015287a19001384fe94dbff84c92ce4ee1, c4d80e41cb42008dceb35e5dbf52574d93beac0d, 52a7c9d930b95aa8b1620edaba4818040c32631f
LinuxLinux Kernel3.2 up to, but not including, 5.4.293; 5.5 up to, but not including, 5.10.237; 5.11 up to, but not including, 5.15.181; 5.16 up to, but not including, 6.1.136; 6.2 up to, but not including, 6.6.89; 6.7 up to, but not including, 6.12.26; 6.13 up to, but not including, 6.14.5; 6.155.4.293, 5.10.237, 5.15.181, 6.1.136, 6.6.89, 6.12.26
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: usb: dwc3: gadget: check that event count does not exceed event buffer length The event count is read from register DWC3_GEVNTCOUNT. There is a check for the count being zero, but not for exceeding the event buffer length. Check that event count does not exceed event buffer length, avoiding an out-of-bounds access when memcpy'ing the event. Crash log: Unable to handle kernel paging request at virtual address ffffffc0129be000 pc : __memcpy+0x114/0x180 lr : dwc3_check_event_buf+0xec/0x348 x3 : 0000000000000030 x2 : 000000000000dfc4 x1 : ffffffc0129be000 x0 : ffffff87aad60080 Call trace: __memcpy+0x114/0x180 dwc3_interrupt+0x24/0x34

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.