CyberSecBulletin
CVE-2023-53019NVD status: Analyzed

Linux: Improper Validation of Array Index

Published Updated By the CyberSecBulletin desk

CVE-2023-53019 is a high-severity improper validation of array index 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 1d80c259dfbadefa61b7ea334dfce5cb57f8c72f, c431a3d642593bbdb99e8a9e3eed608b730db6f8, 8a7b9560a3a8eb8724888c426e05926752f73aa0 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.2% 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 1d80c259dfbadefa61b7ea334dfce5cb57f8c72f or c431a3d642593bbdb99e8a9e3eed608b730db6f8 or 8a7b9560a3a8eb8724888c426e05926752f73aa0 or 4bc5f1f6bc94e695dfd912122af96e7115a0ddb8, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 4.14.305 or 4.19.272 or 5.4.231 or 5.10.166, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux7f854420fbfe9d49afe2ffb1df052cfe8e215541 up to, but not including, 1d80c259dfbadefa61b7ea334dfce5cb57f8c72f; 7f854420fbfe9d49afe2ffb1df052cfe8e215541 up to, but not including, c431a3d642593bbdb99e8a9e3eed608b730db6f8; 7f854420fbfe9d49afe2ffb1df052cfe8e215541 up to, but not including, 8a7b9560a3a8eb8724888c426e05926752f73aa0; 7f854420fbfe9d49afe2ffb1df052cfe8e215541 up to, but not including, 4bc5f1f6bc94e695dfd912122af96e7115a0ddb8; 7f854420fbfe9d49afe2ffb1df052cfe8e215541 up to, but not including, ad67de330d83e8078372b52af18ffe8d39e26c85; 7f854420fbfe9d49afe2ffb1df052cfe8e215541 up to, but not including, 7879626296e6ffd838ae0f2af1ab49ee46354973; 7f854420fbfe9d49afe2ffb1df052cfe8e215541 up to, but not including, 867dbe784c5010a466f00a7d1467c1c5ea569c75; 4.51d80c259dfbadefa61b7ea334dfce5cb57f8c72f, c431a3d642593bbdb99e8a9e3eed608b730db6f8, 8a7b9560a3a8eb8724888c426e05926752f73aa0, 4bc5f1f6bc94e695dfd912122af96e7115a0ddb8, ad67de330d83e8078372b52af18ffe8d39e26c85, 7879626296e6ffd838ae0f2af1ab49ee46354973
LinuxLinux Kernel4.5 up to, but not including, 4.14.305; 4.15 up to, but not including, 4.19.272; 4.20 up to, but not including, 5.4.231; 5.5 up to, but not including, 5.10.166; 5.11 up to, but not including, 5.15.91; 5.16 up to, but not including, 6.1.9; 6.24.14.305, 4.19.272, 5.4.231, 5.10.166, 5.15.91, 6.1.9

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.

Official description

In the Linux kernel, the following vulnerability has been resolved: net: mdio: validate parameter addr in mdiobus_get_phy() The caller may pass any value as addr, what may result in an out-of-bounds access to array mdio_map. One existing case is stmmac_init_phy() that may pass -1 as addr. Therefore validate addr before using it.

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.