CyberSecBulletin
CVE-2024-46713NVD status: Modified

Linux: Out-of-bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2024-46713 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 7882923f1cb88dc1a17f2bf0c81b1fc80d44db82, 52d13d224fdf1299c8b642807fa1ea14d693f5ff, 9dc7ad2b67772cfb94ceb3b0c9c4023c2463215d 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.3% 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 7882923f1cb88dc1a17f2bf0c81b1fc80d44db82 or 52d13d224fdf1299c8b642807fa1ea14d693f5ff or 9dc7ad2b67772cfb94ceb3b0c9c4023c2463215d or c4b69bee3f4ef76809288fe6827bc14d4ae788ef, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 5.10.226 or 5.15.167 or 6.1.110 or 6.6.51, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux45bfb2e50471abbbfd83d40d28c986078b0d24ff up to, but not including, 7882923f1cb88dc1a17f2bf0c81b1fc80d44db82; 45bfb2e50471abbbfd83d40d28c986078b0d24ff up to, but not including, 52d13d224fdf1299c8b642807fa1ea14d693f5ff; 45bfb2e50471abbbfd83d40d28c986078b0d24ff up to, but not including, 9dc7ad2b67772cfb94ceb3b0c9c4023c2463215d; 45bfb2e50471abbbfd83d40d28c986078b0d24ff up to, but not including, c4b69bee3f4ef76809288fe6827bc14d4ae788ef; 45bfb2e50471abbbfd83d40d28c986078b0d24ff up to, but not including, b9b6882e243b653d379abbeaa64a500182aba370; 45bfb2e50471abbbfd83d40d28c986078b0d24ff up to, but not including, 2ab9d830262c132ab5db2f571003d80850d56b2a; 4.17882923f1cb88dc1a17f2bf0c81b1fc80d44db82, 52d13d224fdf1299c8b642807fa1ea14d693f5ff, 9dc7ad2b67772cfb94ceb3b0c9c4023c2463215d, c4b69bee3f4ef76809288fe6827bc14d4ae788ef, b9b6882e243b653d379abbeaa64a500182aba370, 2ab9d830262c132ab5db2f571003d80850d56b2a
LinuxLinux Kernel4.1 up to, but not including, 5.10.226; 5.11 up to, but not including, 5.15.167; 5.16 up to, but not including, 6.1.110; 6.2 up to, but not including, 6.6.51; 6.7 up to, but not including, 6.10.10; 6.115.10.226, 5.15.167, 6.1.110, 6.6.51, 6.10.10

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: perf/aux: Fix AUX buffer serialization Ole reported that event->mmap_mutex is strictly insufficient to serialize the AUX buffer, add a per RB mutex to fully serialize it. Note that in the lock order comment the perf_event::mmap_mutex order was already wrong, that is, it nesting under mmap_lock is not new with this patch.

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.