Security readout for executives and security teams
Plain-English summary
This Linux kernel issue affects AMD display HDCP handling. A field expected to be five bytes was read as eight bytes, which could corrupt values and potentially affect confidentiality or availability. It is rated critical in the supplied CVSS data, but the provided sources do not show active exploitation.
Executive priority
Treat as high-priority patching for Linux endpoints or servers using affected AMD display paths. The critical score justifies urgency, but response should be patch-and-verify rather than incident escalation unless separate telemetry shows exploitation.
Technical view
The flaw is in drm/amd/display HDCP processing. The vulnerable code over-read a five-byte target field as eight bytes, allowing trailing non-zero bytes to corrupt the resulting value. The kernel fix uses a zero-initialized bounce buffer and reads only five bytes before casting to u64.
Likely exposure
Likely exposure is Linux systems running affected kernel versions with the AMD display HDCP code present. The source lists Linux kernel 5.5, 5.10.51, 5.12.18, 5.13.3, and 5.14 data, but distro backport status must be verified with vendor advisories.
Exploitation context
The supplied CVSS vector rates this as network-reachable with no privileges or user interaction. However, the public source text only describes an over-read and corruption bug, and KEV is false. No cited source in the bundle confirms active exploitation or public exploit use.
Researcher notes
The source evidence supports a memory over-read/corruption condition in AMD display HDCP code. The exact practical attack path is not described in the bundle, so avoid assuming exploitability beyond the CVSS vector and kernel fix history.
Mitigation direction
- Update to a kernel containing one of the referenced stable fixes or a vendor backport.
- Check Linux distribution advisories for exact package versions and backport status.
- Prioritize AMD-display workloads where HDCP functionality may be enabled or reachable.
- If immediate patching is delayed, follow vendor guidance for operational mitigations.
Validation and detection
- Inventory Linux kernel versions across AMD display-capable systems.
- Map installed kernels to vendor-fixed packages or referenced upstream stable commits.
- Review asset exposure for systems using AMD DRM display and HDCP functionality.
- Confirm no vulnerable kernel remains after patch deployment and reboot.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-119: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2021-47348 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H3.95.2CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/c5b518f4b98dbb2bc31b6a55e6aaa1e0e2948f2eCVE reference, Linux
- https://git.kernel.org/stable/c/44c7c901cb368a9f2493748f213b247b5872639fCVE reference, Linux
- https://git.kernel.org/stable/c/3b2b93a485fb7a970bc8b5daef16f4cf579d172fCVE reference, Linux
- https://git.kernel.org/stable/c/06888d571b513cbfc0b41949948def6cb81021b2CVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Restriction of Operations within the Bounds of a Memory Buffer
Improper Restriction of Operations within the Bounds of a Memory Buffer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.