CyberSecBulletin
CVE-2022-48655NVD status: Analyzed

Linux: Improper Restriction of Operations within the Bounds of a Memory Buffer

Published Updated By the CyberSecBulletin desk

CVE-2022-48655 is a high-severity improper restriction of operations within the bounds of a memory buffer 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 7184491fc515f391afba23d0e9b690caaea72daf, f2277d9e2a0d092c13bae7ee82d75432bb8b5108, 1f08a1b26cfc53b7715abc46857c6023bb1b87de 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.74% chance of exploitation within 30 days, higher than 55% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Linux to 7184491fc515f391afba23d0e9b690caaea72daf or f2277d9e2a0d092c13bae7ee82d75432bb8b5108 or 1f08a1b26cfc53b7715abc46857c6023bb1b87de or 8e65edf0d37698f7a6cb174608d3ec7976baf49e, whichever matches your release line, or a later version.
  2. Update linux_kernel to 7184491fc515 or f2277d9e2a0d or 1f08a1b26cfc or 8e65edf0d376, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux95a15d80aa0de938299acfcbc6aa6f2b16f5d7e5 up to, but not including, 7184491fc515f391afba23d0e9b690caaea72daf; 95a15d80aa0de938299acfcbc6aa6f2b16f5d7e5 up to, but not including, f2277d9e2a0d092c13bae7ee82d75432bb8b5108; 95a15d80aa0de938299acfcbc6aa6f2b16f5d7e5 up to, but not including, 1f08a1b26cfc53b7715abc46857c6023bb1b87de; 95a15d80aa0de938299acfcbc6aa6f2b16f5d7e5 up to, but not including, 8e65edf0d37698f7a6cb174608d3ec7976baf49e; 95a15d80aa0de938299acfcbc6aa6f2b16f5d7e5 up to, but not including, e9076ffbcaed5da6c182b144ef9f6e24554af268; 5.47184491fc515f391afba23d0e9b690caaea72daf, f2277d9e2a0d092c13bae7ee82d75432bb8b5108, 1f08a1b26cfc53b7715abc46857c6023bb1b87de, 8e65edf0d37698f7a6cb174608d3ec7976baf49e, e9076ffbcaed5da6c182b144ef9f6e24554af268
Linuxlinux_kernel95a15d80aa0d up to, but not including, 7184491fc515; 95a15d80aa0d up to, but not including, f2277d9e2a0d; 95a15d80aa0d up to, but not including, 1f08a1b26cfc; 95a15d80aa0d up to, but not including, 8e65edf0d376; 95a15d80aa0d up to, but not including, e9076ffbcaed; 5.47184491fc515, f2277d9e2a0d, 1f08a1b26cfc, 8e65edf0d376, e9076ffbcaed
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.8HighNVD
CVSS 3.18.1HighCISA (ADP)

Official description

In the Linux kernel, the following vulnerability has been resolved: firmware: arm_scmi: Harden accesses to the reset domains Accessing reset domains descriptors by the index upon the SCMI drivers requests through the SCMI reset operations interface can potentially lead to out-of-bound violations if the SCMI driver misbehave. Add an internal consistency check before any such domains descriptors accesses.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Restriction of Operations within the Bounds of a Memory Buffer

The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary.

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 Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerabilities (CWE-119)

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

Third-party and government advisories

Recent Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerabilities

Spotted an error? Tell us.