CyberSecBulletin
CVE-2022-48967NVD status: Modified

Linux: Improper Validation of Array Index

Published Updated By the CyberSecBulletin desk

CVE-2022-48967 is a high-severity improper validation of array index vulnerability in Linux, with a CVSS 3.1 base score of 7.1 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 6b37f0dc0638d13a006f2f24d2f6ca61e83bc714, dbdcfb9f6748218a149f62468d6297ce3f014e9c, cff35329070b96b4484d23f9f48a5ca2c947e750 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.34% 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 6b37f0dc0638d13a006f2f24d2f6ca61e83bc714 or dbdcfb9f6748218a149f62468d6297ce3f014e9c or cff35329070b96b4484d23f9f48a5ca2c947e750 or 6778434706940b8fad7ef35f410d2b9929f256d2, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 4.9.336 or 4.14.302 or 4.19.269 or 5.4.227, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5 up to, but not including, 6b37f0dc0638d13a006f2f24d2f6ca61e83bc714; 019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5 up to, but not including, dbdcfb9f6748218a149f62468d6297ce3f014e9c; 019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5 up to, but not including, cff35329070b96b4484d23f9f48a5ca2c947e750; 019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5 up to, but not including, 6778434706940b8fad7ef35f410d2b9929f256d2; 019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5 up to, but not including, 27eb2d7a1b9987b6d0429b7716b1ff3b82c4ffc9; 019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5 up to, but not including, 908b2da426fe9c3ce74cf541ba40e7a4251db191; 019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5 up to, but not including, f41547546db9af99da2c34e3368664d7a79cefae; 019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5 up to, but not including, e329e71013c9b5a4535b099208493c7826ee4a64; and 1 more ranges6b37f0dc0638d13a006f2f24d2f6ca61e83bc714, dbdcfb9f6748218a149f62468d6297ce3f014e9c, cff35329070b96b4484d23f9f48a5ca2c947e750, 6778434706940b8fad7ef35f410d2b9929f256d2, 27eb2d7a1b9987b6d0429b7716b1ff3b82c4ffc9, 908b2da426fe9c3ce74cf541ba40e7a4251db191
LinuxLinux Kernel3.4 up to, but not including, 4.9.336; 4.10 up to, but not including, 4.14.302; 4.15 up to, but not including, 4.19.269; 4.20 up to, but not including, 5.4.227; 5.5 up to, but not including, 5.10.159; 5.11 up to, but not including, 5.15.83; 5.16 up to, but not including, 6.0.13; 6.14.9.336, 4.14.302, 4.19.269, 5.4.227, 5.10.159, 5.15.83

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
NoneNo data is disclosed.
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:N/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.18.8HighCNA
CVSS 3.17.1HighNVD

Official description

In the Linux kernel, the following vulnerability has been resolved: NFC: nci: Bounds check struct nfc_target arrays While running under CONFIG_FORTIFY_SOURCE=y, syzkaller reported: memcpy: detected field-spanning write (size 129) of single field "target->sensf_res" at net/nfc/nci/ntf.c:260 (size 18) This appears to be a legitimate lack of bounds checking in nci_add_new_protocol(). Add the missing checks.

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

The underlying weakness: Improper Validation of Array Index

The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array.

How developers prevent this class of flaw

  • Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, Ada allows the programmer to constrain the values of a variable and languages such as Java and Ruby will allow the programmer to handle exceptions when an out-of-bounds index is accessed.
  • Use a CPU and operating system that offers Data Execution Protection (using hardware NX or XD bits) or the equivalent techniques that simulate this feature in software, such as PaX. These techniques ensure that any instruction executed is exclusively at a memory address that is part of the code segment. For more information on these techniques see D3-PSEP (Process Segment Execution Prevention) from D3FEND.

More Improper Validation of Array Index vulnerabilities (CWE-129)

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 Improper Validation of Array Index vulnerabilities

Spotted an error? Tell us.