SECUFOCUSNOW
Home›CVE index›CVE-2024-46818
Review reviewHigh

CVE-2024-46818

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check gpio_id before used as array index [WHY & HOW] GPIO_ID_UNKNOWN (-1) is not a valid value for array index and therefore should be checked in advance. This fixes 5 OVERRUN issues reported by Coverity.

CVSS
7.8
EPSS
-
- percentile
CISA KEV
Not listed
Published
2024.09.27
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability-
Technical severityCVSS 7.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check gpio_id before used as array index [WHY & HOW] GPIO_ID_UNKNOWN (-1) is not a valid value for array index and therefore should be checked in advance. This fixes 5 OVERRUN issues reported by Coverity.

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c < 8520fdc8ecc38f240a8e9e7af89cca6739c3e790, >= 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c < 40c2e8bc117cab8bca8814735f28a8b121654a84, >= 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c < 0184cca30cad74d88f5c875d4e26999e26325700, >= 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c < 276e3fd93e3beb5894eb1cc8480f9f417d51524d, >= 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c < 08e7755f754e3d2cef7d3a7da538d33526bd6f7c, >= 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c < 3d4198ab612ad48f73383ad3bb5663e6f0cdf406, >= 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c < 2a5626eeb3b5eec7a36886f9556113dd93ec8ed6, >= 4.15, < 5.4.284, >= 5.5 < 5.10.226, >= 5.11 < 5.15.167, >= 5.16 < 6.1.109, >= 6.2 < 6.6.50, >= 6.7 < 6.10.9
Fixed versions
5.4.284, 5.10.226, 5.15.167, 6.1.109, 6.6.50, 6.10.9

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-129