CyberSecBulletin
CVE-2025-38456NVD status: Modified

Linux: Out-of-bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2025-38456 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 cbc1670297f675854e982d23c8583900ff0cc67a, e2d5c005dfc96fe857676d1d8ac46b29275cb89b, 9e0d33e75c1604c3fad5586ad4dfa3b2695a3950 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.19% 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 cbc1670297f675854e982d23c8583900ff0cc67a or e2d5c005dfc96fe857676d1d8ac46b29275cb89b or 9e0d33e75c1604c3fad5586ad4dfa3b2695a3950 or 7c1a6ddb99858e7d68961f74ae27caeeeca67b6a, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 6.1.146 or 6.6.99 or 6.12.39 or 6.15.7, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux8e76741c3d8b20dfa2d6c30fa10ff927cfd93d82 up to, but not including, cbc1670297f675854e982d23c8583900ff0cc67a; 8e76741c3d8b20dfa2d6c30fa10ff927cfd93d82 up to, but not including, e2d5c005dfc96fe857676d1d8ac46b29275cb89b; 8e76741c3d8b20dfa2d6c30fa10ff927cfd93d82 up to, but not including, 9e0d33e75c1604c3fad5586ad4dfa3b2695a3950; 8e76741c3d8b20dfa2d6c30fa10ff927cfd93d82 up to, but not including, 7c1a6ddb99858e7d68961f74ae27caeeeca67b6a; 8e76741c3d8b20dfa2d6c30fa10ff927cfd93d82 up to, but not including, fa332f5dc6fc662ad7d3200048772c96b861cf6b; 5.19cbc1670297f675854e982d23c8583900ff0cc67a, e2d5c005dfc96fe857676d1d8ac46b29275cb89b, 9e0d33e75c1604c3fad5586ad4dfa3b2695a3950, 7c1a6ddb99858e7d68961f74ae27caeeeca67b6a, fa332f5dc6fc662ad7d3200048772c96b861cf6b
LinuxLinux Kernel5.19 up to, but not including, 6.1.146; 6.2 up to, but not including, 6.6.99; 6.7 up to, but not including, 6.12.39; 6.13 up to, but not including, 6.15.76.1.146, 6.6.99, 6.12.39, 6.15.7
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: ipmi:msghandler: Fix potential memory corruption in ipmi_create_user() The "intf" list iterator is an invalid pointer if the correct "intf->intf_num" is not found. Calling atomic_dec(&intf->nr_users) on and invalid pointer will lead to memory corruption. We don't really need to call atomic_dec() if we haven't called atomic_add_return() so update the if (intf->in_shutdown) path as well.

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.