CyberSecBulletin
CVE-2024-26763NVD status: Modified

Linux: Out-of-bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2024-26763 is a high-severity out-of-bounds write vulnerability in Linux, with a CVSS 3.1 base score of 7.1 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 43a202bd552976497474ae144942e32cc5f34d7e, 0dccbb93538fe89a86c6de31d4b1c8c560848eaa, 3c652f6fa1e1f9f02c3fbf359d260ad153ec5f90 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 43a202bd552976497474ae144942e32cc5f34d7e or 0dccbb93538fe89a86c6de31d4b1c8c560848eaa or 3c652f6fa1e1f9f02c3fbf359d260ad153ec5f90 or 1a4371db68a31076afbe56ecce34fbbe6c80c529, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 4.19.308 or 5.4.270 or 5.10.211 or 5.15.150, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxef43aa38063a6b2b3c6618e28ab35794f4f1fe29 up to, but not including, 43a202bd552976497474ae144942e32cc5f34d7e; ef43aa38063a6b2b3c6618e28ab35794f4f1fe29 up to, but not including, 0dccbb93538fe89a86c6de31d4b1c8c560848eaa; ef43aa38063a6b2b3c6618e28ab35794f4f1fe29 up to, but not including, 3c652f6fa1e1f9f02c3fbf359d260ad153ec5f90; ef43aa38063a6b2b3c6618e28ab35794f4f1fe29 up to, but not including, 1a4371db68a31076afbe56ecce34fbbe6c80c529; ef43aa38063a6b2b3c6618e28ab35794f4f1fe29 up to, but not including, e08c2a8d27e989f0f5b0888792643027d7e691e6; ef43aa38063a6b2b3c6618e28ab35794f4f1fe29 up to, but not including, 64ba01a365980755732972523600a961c4266b75; ef43aa38063a6b2b3c6618e28ab35794f4f1fe29 up to, but not including, d9e3763a505e50ba3bd22846f2a8db99429fb857; ef43aa38063a6b2b3c6618e28ab35794f4f1fe29 up to, but not including, 50c70240097ce41fe6bce6478b80478281e4d0f7; and 1 more ranges43a202bd552976497474ae144942e32cc5f34d7e, 0dccbb93538fe89a86c6de31d4b1c8c560848eaa, 3c652f6fa1e1f9f02c3fbf359d260ad153ec5f90, 1a4371db68a31076afbe56ecce34fbbe6c80c529, e08c2a8d27e989f0f5b0888792643027d7e691e6, 64ba01a365980755732972523600a961c4266b75
LinuxLinux Kernelbefore 4.19.308; 4.20 up to, but not including, 5.4.270; 5.5 up to, but not including, 5.10.211; 5.11 up to, but not including, 5.15.150; 5.16 up to, but not including, 6.1.80; 6.2 up to, but not including, 6.6.19; 6.7 up to, but not including, 6.7.7; 6.84.19.308, 5.4.270, 5.10.211, 5.15.150, 6.1.80, 6.6.19
DebianDebian Linux10.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
NoneNo data is disclosed.
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:N/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.17.1HighCNA
CVSS 3.17.1HighNVD

Official description

In the Linux kernel, the following vulnerability has been resolved: dm-crypt: don't modify the data when using authenticated encryption It was said that authenticated encryption could produce invalid tag when the data that is being encrypted is modified [1]. So, fix this problem by copying the data into the clone bio first and then encrypt them inside the clone bio. This may reduce performance, but it is needed to prevent the user from corrupting the device by writing data with O_DIRECT and modifying them at the same time. [1] https://lore.kernel.org/all/[email protected]/T/

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. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Out-of-bounds Write vulnerabilities

Spotted an error? Tell us.