CyberSecBulletin
CVE-2025-38401NVD status: Modified

Linux: Out-of-bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2025-38401 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 5ac9e9e2e9cd6247d8c2d99780eae4556049e1cc, d54771571f74a82c59830a32e76af78a8e57ac69, 48bf4f3dfcdab02b22581d8e350a2d23130b72c0 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.21% 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 5ac9e9e2e9cd6247d8c2d99780eae4556049e1cc or d54771571f74a82c59830a32e76af78a8e57ac69 or 48bf4f3dfcdab02b22581d8e350a2d23130b72c0 or 63e8953f16acdcb23e2d4dd8a566d3c34df3e200, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 5.4.296 or 5.10.240 or 5.15.187 or 6.1.144, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux208489032bdd8d4a7de50f3057c175058f271956 up to, but not including, 5ac9e9e2e9cd6247d8c2d99780eae4556049e1cc; 208489032bdd8d4a7de50f3057c175058f271956 up to, but not including, d54771571f74a82c59830a32e76af78a8e57ac69; 208489032bdd8d4a7de50f3057c175058f271956 up to, but not including, 48bf4f3dfcdab02b22581d8e350a2d23130b72c0; 208489032bdd8d4a7de50f3057c175058f271956 up to, but not including, 63e8953f16acdcb23e2d4dd8a566d3c34df3e200; 208489032bdd8d4a7de50f3057c175058f271956 up to, but not including, 61cdd663564674ea21ceb50aa9d3697cbe9e45f9; 208489032bdd8d4a7de50f3057c175058f271956 up to, but not including, 3419bc6a7b65cbbb91417bb9970208478e034c79; 208489032bdd8d4a7de50f3057c175058f271956 up to, but not including, a5f5f67b284d81776d4a3eb1f8607e4b7f91f11c; 208489032bdd8d4a7de50f3057c175058f271956 up to, but not including, f5de469990f19569627ea0dd56536ff5a13beaa3; and 1 more ranges5ac9e9e2e9cd6247d8c2d99780eae4556049e1cc, d54771571f74a82c59830a32e76af78a8e57ac69, 48bf4f3dfcdab02b22581d8e350a2d23130b72c0, 63e8953f16acdcb23e2d4dd8a566d3c34df3e200, 61cdd663564674ea21ceb50aa9d3697cbe9e45f9, 3419bc6a7b65cbbb91417bb9970208478e034c79
LinuxLinux Kernel4.2 up to, but not including, 5.4.296; 5.5 up to, but not including, 5.10.240; 5.11 up to, but not including, 5.15.187; 5.16 up to, but not including, 6.1.144; 6.2 up to, but not including, 6.6.97; 6.7 up to, but not including, 6.12.37; 6.13 up to, but not including, 6.15.6; 6.165.4.296, 5.10.240, 5.15.187, 6.1.144, 6.6.97, 6.12.37
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: mtk-sd: Prevent memory corruption from DMA map failure If msdc_prepare_data() fails to map the DMA region, the request is not prepared for data receiving, but msdc_start_data() proceeds the DMA with previous setting. Since this will lead a memory corruption, we have to stop the request operation soon after the msdc_prepare_data() fails to prepare it.

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

Recent Out-of-bounds Write vulnerabilities

Spotted an error? Tell us.