CyberSecBulletin
CVE-2022-48717NVD status: Modified

Linux: Out-of-bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2022-48717 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 a0f49d12547d45ea8b0f356a96632dd503941c1e, 71e60c170105d153e34d01766c1e4db26a4b24cc, 5a45448ac95b715173edb1cd090ff24b6586d921 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.22% 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 a0f49d12547d45ea8b0f356a96632dd503941c1e or 71e60c170105d153e34d01766c1e4db26a4b24cc or 5a45448ac95b715173edb1cd090ff24b6586d921 or baead410e5db49e962a67fffc17ac30e44b50b7c, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 4.19.228 or 5.4.178 or 5.10.99 or 5.15.22, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxfa8d915172b8c10ec0734c4021e99e9705023b07 up to, but not including, a0f49d12547d45ea8b0f356a96632dd503941c1e; fa8d915172b8c10ec0734c4021e99e9705023b07 up to, but not including, 71e60c170105d153e34d01766c1e4db26a4b24cc; fa8d915172b8c10ec0734c4021e99e9705023b07 up to, but not including, 5a45448ac95b715173edb1cd090ff24b6586d921; fa8d915172b8c10ec0734c4021e99e9705023b07 up to, but not including, baead410e5db49e962a67fffc17ac30e44b50b7c; fa8d915172b8c10ec0734c4021e99e9705023b07 up to, but not including, f114fd6165dfb52520755cc4d1c1dfbd447b88b6; fa8d915172b8c10ec0734c4021e99e9705023b07 up to, but not including, 4c907bcd9dcd233da6707059d777ab389dcbd964; 4.17a0f49d12547d45ea8b0f356a96632dd503941c1e, 71e60c170105d153e34d01766c1e4db26a4b24cc, 5a45448ac95b715173edb1cd090ff24b6586d921, baead410e5db49e962a67fffc17ac30e44b50b7c, f114fd6165dfb52520755cc4d1c1dfbd447b88b6, 4c907bcd9dcd233da6707059d777ab389dcbd964
LinuxLinux Kernel4.17 up to, but not including, 4.19.228; 4.20 up to, but not including, 5.4.178; 5.5 up to, but not including, 5.10.99; 5.11 up to, but not including, 5.15.22; 5.16 up to, but not including, 5.16.8; 5.174.19.228, 5.4.178, 5.10.99, 5.15.22, 5.16.8

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.1HighCNA
CVSS 3.17.8HighNVD

Official description

In the Linux kernel, the following vulnerability has been resolved: ASoC: max9759: fix underflow in speaker_gain_control_put() Check for negative values of "priv->gain" to prevent an out of bounds access. The concern is that these might come from the user via: -> snd_ctl_elem_write_user() -> snd_ctl_elem_write() -> kctl->put()

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.