Review reviewHigh

CVE-2021-47535

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: drm/msm/a6xx: Allocate enough space for GMU registers In commit 142639a52a01 ("drm/msm/a6xx: fix crashstate capture for A650") we changed a6xx_get_gmu_registers() to read 3 sets of registers. Unfortunately, we didn't change the memory allocation for the array. That leads to a KASAN warning (this was on the chromeos-5.4 kernel, which has the problematic commit backported to it): BUG: KASAN: slab-out-of-bounds in _a6xx_get_gmu_registers+0x144/0x430 Write of size 8 at addr ffffff80c89432b0 by task A618-worker/209 CPU: 5 PID: 2...

CVSS
7.8
EPSS
0.24%
14.6% percentile
CISA KEV
Not listed
Published
2024.05.25
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.24%
Technical severityCVSS 7.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: drm/msm/a6xx: Allocate enough space for GMU registers In commit 142639a52a01 ("drm/msm/a6xx: fix crashstate capture for A650") we changed a6xx_get_gmu_registers() to read 3 sets of registers. Unfortunately, we didn't change the memory allocation for the array. That leads to a KASAN warning (this was on the chromeos-5.4 kernel, which has the problematic commit backported to it): BUG: KASAN: slab-out-of-bounds in _a6xx_get_gmu_registers+0x144/0x430 Write of size 8 at addr ffffff80c89432b0 by task A618-worker/209 CPU: 5 PID: 2...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 142639a52a01e90c512a9a8d2156997e02a65b53 < d646856a600e8635ba498f20b194219b158626e8, >= 142639a52a01e90c512a9a8d2156997e02a65b53 < 83e54fcf0b14ca2d869dd37abe1bb6542805f538, >= 142639a52a01e90c512a9a8d2156997e02a65b53 < b4d25abf9720b69a03465b09d0d62d1998ed6708, >= 5.9, >= 5.9 < 5.10.84, >= 5.11 < 5.15.7, 5.16
Fixed versions
5.10.84, 5.15.7

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-787
CVE-2021-47535 — Linux Linux, linux kernel | SECUFOCUS NOW