CVE-2021-47489

Kernel memory corruption via mismatched debugfs buffer length

Published May 22, 2024 · Updated May 11, 2026

Out-of-bounds writes in the Linux kernel allow local users to corrupt kernel memory through crafted AMD GPU debugfs control input. Nine write handlers in amdgpu_dm_debugfs.c pass the user-supplied byte count rather than the allocated buffer size to parse_write_buffer_into_params, allowing the parser to write beyond the heap buffer. Reachability requires local access to writable AMD GPU debugfs controls, which are root-only by default; a successful write compromises kernel confidentiality, integrity, and availability.

CVSS severity7.8
High
EPSS probability0.22%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Out-of-bounds writes in the Linux kernel allow local users to corrupt kernel memory through crafted AMD GPU debugfs control input. Nine write handlers in amdgpu_dm_debugfs.c pass the user-supplied byte count rather than the allocated buffer size to parse_write_buffer_into_params, allowing the parser to write beyond the heap buffer. Reachability requires local access to writable AMD GPU debugfs controls, which are root-only by default; a successful write compromises kernel confidentiality, integrity, and availability.

The record

CVE
CVE-2021-47489
Published
May 22, 2024
Updated
May 11, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
CWE-787, T1068
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. May 22, 2024CVE publishedPublication date reported by the CVE source.
  2. May 11, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=5.10
  2. Affected versionversion=918698d5c2b50433714d2042f55b55b090faa167 <1336b886b162fdc84708096ea152a61c0e1fc09c
  3. Affected versionversion=918698d5c2b50433714d2042f55b55b090faa167 <3f4e54bd312d3dafb59daf2b97ffa08abebe60f5
  4. Affected versionversion=918698d5c2b50433714d2042f55b55b090faa167 <9eb4bdd554fc31a5ef6bf645a20ff21618ce45a9

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=5.10; version=918698d5c2b50433714d2042f55b55b090faa167 <1336b886b162fdc84708096ea152a61c0e1fc09c; version=918698d5c2b50433714d2042f55b55b090faa167 <3f4e54bd312d3dafb59daf2b97ffa08abebe60f5; version=918698d5c2b50433714d2042f55b55b090faa167 <9eb4bdd554fc31a5ef6bf645a20ff21618ce45a9

Published CVSS scores

7.8NIST NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-787Out-of-bounds Write
T1068Exploitation for Privilege Escalation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo