CyberSecBulletin
CVE-2024-47698NVD status: Modified

Linux: Out-of-bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2024-47698 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 7065c05c6d58b9b9a98127aa14e9a5ec68173918, 49b33c38d202d3327dcfd058e27f541dcc308b92, 6ae3b9aee42616ee93c4585174f40c767828006d 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.27% 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 7065c05c6d58b9b9a98127aa14e9a5ec68173918 or 49b33c38d202d3327dcfd058e27f541dcc308b92 or 6ae3b9aee42616ee93c4585174f40c767828006d or a879b6cdd48134a3d58949ea4f075c75fa2d7d71, 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
LinuxLinux4b01e01a81b6629878344430531ced347cc2ed5b up to, but not including, 7065c05c6d58b9b9a98127aa14e9a5ec68173918; 4b01e01a81b6629878344430531ced347cc2ed5b up to, but not including, 49b33c38d202d3327dcfd058e27f541dcc308b92; 4b01e01a81b6629878344430531ced347cc2ed5b up to, but not including, 6ae3b9aee42616ee93c4585174f40c767828006d; 4b01e01a81b6629878344430531ced347cc2ed5b up to, but not including, a879b6cdd48134a3d58949ea4f075c75fa2d7d71; 4b01e01a81b6629878344430531ced347cc2ed5b up to, but not including, 15bea004e939d938a6771dfcf2a26cc899ffd20a; 4b01e01a81b6629878344430531ced347cc2ed5b up to, but not including, 527ab3eb3b0b4a6ee00e183c1de6a730239e2835; 4b01e01a81b6629878344430531ced347cc2ed5b up to, but not including, 66dbe0df6eccc7ee53a2c35016ce81e13b3ff447; 4b01e01a81b6629878344430531ced347cc2ed5b up to, but not including, bedd42e07988dbdd124b23e758ffef7a681b9c60; and 2 more ranges7065c05c6d58b9b9a98127aa14e9a5ec68173918, 49b33c38d202d3327dcfd058e27f541dcc308b92, 6ae3b9aee42616ee93c4585174f40c767828006d, a879b6cdd48134a3d58949ea4f075c75fa2d7d71, 15bea004e939d938a6771dfcf2a26cc899ffd20a, 527ab3eb3b0b4a6ee00e183c1de6a730239e2835
DebianDebian Linux11.0Not stated
LinuxLinux Kernel4.0 up to, but not including, 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.54; 6.7 up to, but not including, 6.10.13; 6.11 up to, but not including, 6.11.24.19.323, 5.4.285, 5.10.227, 5.15.168, 6.1.113, 6.6.54

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: drivers: media: dvb-frontends/rtl2832: fix an out-of-bounds write error Ensure index in rtl2832_pid_filter does not exceed 31 to prevent out-of-bounds access. dev->filters is a 32-bit value, so set_bit and clear_bit functions should only operate on indices from 0 to 31. If index is 32, it will attempt to access a non-existent 33rd bit, leading to out-of-bounds access. Change the boundary check from index > 32 to index >= 32 to resolve this issue. [hverkuil: added fixes tag, rtl2830_pid_filter -> rtl2832_pid_filter in logmsg]

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.