CyberSecBulletin
CVE-2022-49581NVD status: Modified

Linux: Out-of-bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2022-49581 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 a5a8fc0679a8fd58d47aa2ebcfc5742631f753f9, fe4473fc7940f14c4a12db873b9729134c212654, 8ff4f9df73e5c551a72ee6034886c17e8de6596d 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.31% 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 a5a8fc0679a8fd58d47aa2ebcfc5742631f753f9 or fe4473fc7940f14c4a12db873b9729134c212654 or 8ff4f9df73e5c551a72ee6034886c17e8de6596d or a8569f76df7ec5b4b51155c57523a0b356db5741, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 4.9.325 or 4.14.290 or 4.19.254 or 5.4.208, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxe36edd9d26cf257511548edaf2b7a56eb4fed854 up to, but not including, a5a8fc0679a8fd58d47aa2ebcfc5742631f753f9; e36edd9d26cf257511548edaf2b7a56eb4fed854 up to, but not including, fe4473fc7940f14c4a12db873b9729134c212654; e36edd9d26cf257511548edaf2b7a56eb4fed854 up to, but not including, 8ff4f9df73e5c551a72ee6034886c17e8de6596d; e36edd9d26cf257511548edaf2b7a56eb4fed854 up to, but not including, a8569f76df7ec5b4b51155c57523a0b356db5741; e36edd9d26cf257511548edaf2b7a56eb4fed854 up to, but not including, 665cbe91de2f7c97c51ca8fce39aae26477c1948; e36edd9d26cf257511548edaf2b7a56eb4fed854 up to, but not including, aba8ff847f4f927ad7a1a1ee4a9f29989a1a728f; e36edd9d26cf257511548edaf2b7a56eb4fed854 up to, but not including, 18043da94c023f3ef09c15017bdb04e8f695ef10; e36edd9d26cf257511548edaf2b7a56eb4fed854 up to, but not including, d7241f679a59cfe27f92cb5c6272cb429fb1f7ec; and 1 more rangesa5a8fc0679a8fd58d47aa2ebcfc5742631f753f9, fe4473fc7940f14c4a12db873b9729134c212654, 8ff4f9df73e5c551a72ee6034886c17e8de6596d, a8569f76df7ec5b4b51155c57523a0b356db5741, 665cbe91de2f7c97c51ca8fce39aae26477c1948, aba8ff847f4f927ad7a1a1ee4a9f29989a1a728f
LinuxLinux Kernel3.18 up to, but not including, 4.9.325; 4.10 up to, but not including, 4.14.290; 4.15 up to, but not including, 4.19.254; 4.20 up to, but not including, 5.4.208; 5.5 up to, but not including, 5.10.134; 5.11 up to, but not including, 5.15.58; 5.16 up to, but not including, 5.18.15; 5.194.9.325, 4.14.290, 4.19.254, 5.4.208, 5.10.134, 5.15.58

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: be2net: Fix buffer overflow in be_get_module_eeprom be_cmd_read_port_transceiver_data assumes that it is given a buffer that is at least PAGE_DATA_LEN long, or twice that if the module supports SFF 8472. However, this is not always the case. Fix this by passing the desired offset and length to be_cmd_read_port_transceiver_data so that we only copy the bytes once.

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.