CyberSecBulletin
CVE-2024-26965NVD status: Modified

Linux: Out-of-bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2024-26965 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 99740c4791dc8019b0d758c5389ca6d1c0604d95, 86bf75d9158f511db7530bc82a84b19a5134d089, 3ff4a0f6a8f0ad4b4ee9e908bdfc3cacb7be4060 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.26% 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 99740c4791dc8019b0d758c5389ca6d1c0604d95 or 86bf75d9158f511db7530bc82a84b19a5134d089 or 3ff4a0f6a8f0ad4b4ee9e908bdfc3cacb7be4060 or 8f562f3b25177c2055b20fd8cf000496f6fa9194, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 4.19.312 or 5.4.274 or 5.10.215 or 5.15.154, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxd8b212014e69d6b6323773ce6898f224ef4ed0d6 up to, but not including, 99740c4791dc8019b0d758c5389ca6d1c0604d95; d8b212014e69d6b6323773ce6898f224ef4ed0d6 up to, but not including, 86bf75d9158f511db7530bc82a84b19a5134d089; d8b212014e69d6b6323773ce6898f224ef4ed0d6 up to, but not including, 3ff4a0f6a8f0ad4b4ee9e908bdfc3cacb7be4060; d8b212014e69d6b6323773ce6898f224ef4ed0d6 up to, but not including, 8f562f3b25177c2055b20fd8cf000496f6fa9194; d8b212014e69d6b6323773ce6898f224ef4ed0d6 up to, but not including, 537040c257ab4cd0673fbae048f3940c8ea2e589; d8b212014e69d6b6323773ce6898f224ef4ed0d6 up to, but not including, 7e9926fef71e514b4a8ea9d11d5a84d52b181362; d8b212014e69d6b6323773ce6898f224ef4ed0d6 up to, but not including, ae99e199037c580b7350bfa3596f447a53bcf01f; d8b212014e69d6b6323773ce6898f224ef4ed0d6 up to, but not including, ca2cf98d46748373e830a13d85d215d64a2d9bf2; and 2 more ranges99740c4791dc8019b0d758c5389ca6d1c0604d95, 86bf75d9158f511db7530bc82a84b19a5134d089, 3ff4a0f6a8f0ad4b4ee9e908bdfc3cacb7be4060, 8f562f3b25177c2055b20fd8cf000496f6fa9194, 537040c257ab4cd0673fbae048f3940c8ea2e589, 7e9926fef71e514b4a8ea9d11d5a84d52b181362
LinuxLinux Kernel3.14 up to, but not including, 4.19.312; 4.20 up to, but not including, 5.4.274; 5.5 up to, but not including, 5.10.215; 5.11 up to, but not including, 5.15.154; 5.16 up to, but not including, 6.1.84; 6.2 up to, but not including, 6.6.24; 6.7 up to, but not including, 6.7.12; 6.8 up to, but not including, 6.8.34.19.312, 5.4.274, 5.10.215, 5.15.154, 6.1.84, 6.6.24
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
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.3HighCNA
CVSS 3.17.8HighNVD

Official description

In the Linux kernel, the following vulnerability has been resolved: clk: qcom: mmcc-msm8974: fix terminating of frequency table arrays The frequency table arrays are supposed to be terminated with an empty element. Add such entry to the end of the arrays where it is missing in order to avoid possible out-of-bound access when the table is traversed by functions like qcom_find_freq() or qcom_find_freq_floor(). Only compile tested.

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

Third-party and government advisories

Recent Out-of-bounds Write vulnerabilities

Spotted an error? Tell us.