CyberSecBulletin
CVE-2024-36978NVD status: Modified

Linux: Out-of-bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2024-36978 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 d5d9d241786f49ae7cbc08e7fc95a115e9d80f3d, 52b1aa07cda6a199cd6754d3798c7759023bc70f, 598572c64287aee0b75bbba4e2881496878860f3 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.28% 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 d5d9d241786f49ae7cbc08e7fc95a115e9d80f3d or 52b1aa07cda6a199cd6754d3798c7759023bc70f or 598572c64287aee0b75bbba4e2881496878860f3 or 0f208fad86631e005754606c3ec80c0d44a11882, whichever matches your release line, or a later version.
  2. Update RUGGEDCOM RST2428P to V3.1 or a later version.
  3. Update SCALANCE XCM-/XRM-/XCH-/XRH-300 family to V3.1 or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxc2999f7fb05b87da4060e38150c70fa46794d82b up to, but not including, d5d9d241786f49ae7cbc08e7fc95a115e9d80f3d; c2999f7fb05b87da4060e38150c70fa46794d82b up to, but not including, 52b1aa07cda6a199cd6754d3798c7759023bc70f; c2999f7fb05b87da4060e38150c70fa46794d82b up to, but not including, 598572c64287aee0b75bbba4e2881496878860f3; c2999f7fb05b87da4060e38150c70fa46794d82b up to, but not including, 0f208fad86631e005754606c3ec80c0d44a11882; c2999f7fb05b87da4060e38150c70fa46794d82b up to, but not including, 54c2c171c11a798fe887b3ff72922aa9d1411c1e; c2999f7fb05b87da4060e38150c70fa46794d82b up to, but not including, d6fb5110e8722bc00748f22caeb650fe4672f129; c2999f7fb05b87da4060e38150c70fa46794d82b up to, but not including, affc18fdc694190ca7575b9a86632a73b9fe043d; 5.4d5d9d241786f49ae7cbc08e7fc95a115e9d80f3d, 52b1aa07cda6a199cd6754d3798c7759023bc70f, 598572c64287aee0b75bbba4e2881496878860f3, 0f208fad86631e005754606c3ec80c0d44a11882, 54c2c171c11a798fe887b3ff72922aa9d1411c1e, d6fb5110e8722bc00748f22caeb650fe4672f129
SiemensRUGGEDCOM RST2428Pbefore V3.1V3.1
SiemensSCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 familyNot specified in the recordNot stated
SiemensSCALANCE XCM-/XRM-/XCH-/XRH-300 familybefore V3.1V3.1
SiemensSIMATIC S7-1500 TM MFP - GNU/Linux subsystembefore V1.1.1V1.1.1
LinuxLinux Kernel5.4 up to, but not including, 5.4.279; 5.5 up to, but not including, 5.10.221; 5.11 up to, but not including, 5.15.162; 5.16 up to, but not including, 6.1.95; 6.2 up to, but not including, 6.6.35; 6.7 up to, but not including, 6.9.6; 6.105.4.279, 5.10.221, 5.15.162, 6.1.95, 6.6.35, 6.9.6

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: net: sched: sch_multiq: fix possible OOB write in multiq_tune() q->bands will be assigned to qopt->bands to execute subsequent code logic after kmalloc. So the old q->bands should not be used in kmalloc. Otherwise, an out-of-bounds write will occur.

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: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Out-of-bounds Write vulnerabilities

Spotted an error? Tell us.