CyberSecBulletin
CVE-2024-50180NVD status: Modified

Linux: Out-of-bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2024-50180 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 433c84c8495008922534c5cafdae6ff970fb3241, 57c4f4db0a194416da237fd09dad9527e00cb587, 252f147b1826cbb30ae0304cf86b66d3bb12b743 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 433c84c8495008922534c5cafdae6ff970fb3241 or 57c4f4db0a194416da237fd09dad9527e00cb587 or 252f147b1826cbb30ae0304cf86b66d3bb12b743 or 41cf6f26abe4f491b694c54bd1aa2530369b7510, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 4.19.323 or 5.4.285 or 5.10.227 or 5.15.168, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, 433c84c8495008922534c5cafdae6ff970fb3241; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, 57c4f4db0a194416da237fd09dad9527e00cb587; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, 252f147b1826cbb30ae0304cf86b66d3bb12b743; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, 41cf6f26abe4f491b694c54bd1aa2530369b7510; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, 889304120ecb2ca30674d89cd4ef15990b6a571c; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, 688872c4ea4a528cd6a057d545c83506b533ee1f; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, 11c0d49093b82f6c547fd419c41a982d26bdf5ef; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, 9cf14f5a2746c19455ce9cb44341b5527b5e19c3; and 1 more ranges433c84c8495008922534c5cafdae6ff970fb3241, 57c4f4db0a194416da237fd09dad9527e00cb587, 252f147b1826cbb30ae0304cf86b66d3bb12b743, 41cf6f26abe4f491b694c54bd1aa2530369b7510, 889304120ecb2ca30674d89cd4ef15990b6a571c, 688872c4ea4a528cd6a057d545c83506b533ee1f
LinuxLinux Kernelbefore 4.19.323; 4.20 up to, but not including, 5.4.285; 5.5 up to, but not including, 5.10.227; 5.11 up to, but not including, 5.15.168; 5.16 up to, but not including, 6.1.113; 6.2 up to, but not including, 6.6.57; 6.7 up to, but not including, 6.11.44.19.323, 5.4.285, 5.10.227, 5.15.168, 6.1.113, 6.6.57

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.8HighNVD
CVSS 3.17.8HighCISA (ADP)

Official description

In the Linux kernel, the following vulnerability has been resolved: fbdev: sisfb: Fix strbuf array overflow The values of the variables xres and yres are placed in strbuf. These variables are obtained from strbuf1. The strbuf1 array contains digit characters and a space if the array contains non-digit characters. Then, when executing sprintf(strbuf, "%ux%ux8", xres, yres); more than 16 bytes will be written to strbuf. It is suggested to increase the size of the strbuf array to 24. Found by Linux Verification Center (linuxtesting.org) with SVACE.

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.