Home/CVE/In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Avoid HDCP over-read and corruptio
CVE
CVE-2021-47348
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Avoid HDCP over-read and corruptio
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Avoid HDCP over-read and corruption Instead of reading the desired 5 bytes of the actual target field, the code was reading 8. This could result in a corrupted value if the trailing 3 bytes were non-zero, so instead use an appropriately sized and zero-initialized bounce buffer, and read only 5 bytes before casting to u64.
CRITICAL · CVSS 9.1
EPSS 0.00056
Schedule remediation
- SSVC automatable: yes - attacks can be scripted at scale
- CVSS base score ≥ 7.0
Sigma rules0
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2021-47348, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
◆
ATT&CK techniques
1Techniques this CVE enables - linked via CWECAPECATT&CK. High◆ = named directly in ATT&CK or Nuclei templates.
▤ Build a SIEM detection for these techniques▤
CAPEC attack patterns
12Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.
CAPEC-CAPEC-10 · Buffer Overflow via Environment Variables CAPEC-CAPEC-100 · Overflow Buffers CAPEC-CAPEC-123 · Buffer Manipulation CAPEC-CAPEC-14 · Client-side Injection-induced Buffer Overflow CAPEC-CAPEC-24 · Filter Failure through Buffer Overflow CAPEC-CAPEC-42 · MIME Conversion CAPEC-CAPEC-44 · Overflow Binary Resource File CAPEC-CAPEC-45 · Buffer Overflow via Symbolic Links CAPEC-CAPEC-46 · Overflow Variables and Tags CAPEC-CAPEC-47 · Buffer Overflow via Parameter Expansion CAPEC-CAPEC-8 · Buffer Overflow in an API Call CAPEC-CAPEC-9 · Buffer Overflow in Local Command-Line Utilities
⬡
Weakness Classification
▤
Affected Products & Versions
3▤
Affected Packages
40Language-ecosystem packages (from OSV) tied to this CVE, with the version that fixes it - the dependency-level detail NVD doesn’t carry.
Ubuntu:20.04:LTS
linux
Ubuntu:20.04:LTS
linux-aws
Ubuntu:20.04:LTS
linux-aws-5.11
Ubuntu:20.04:LTS
linux-aws-5.13
Ubuntu:20.04:LTS
linux-aws-5.15
fixed in 5.15.0-1014.18~20.04.1
Ubuntu:20.04:LTS
linux-aws-5.8
Ubuntu:20.04:LTS
linux-azure
Ubuntu:20.04:LTS
linux-azure-5.11
Ubuntu:20.04:LTS
linux-azure-5.13
Ubuntu:20.04:LTS
linux-azure-5.15
fixed in 5.15.0-1007.8~20.04.1
Ubuntu:20.04:LTS
linux-azure-5.8
Ubuntu:20.04:LTS
linux-azure-fde
Ubuntu:20.04:LTS
linux-azure-fde-5.15
fixed in 5.15.0-1019.24~20.04.1.1
Ubuntu:20.04:LTS
linux-bluefield
Ubuntu:20.04:LTS
linux-gcp
Ubuntu:20.04:LTS
linux-gcp-5.11
Ubuntu:20.04:LTS
linux-gcp-5.13
Ubuntu:20.04:LTS
linux-gcp-5.15
fixed in 5.15.0-1006.9~20.04.1
Ubuntu:20.04:LTS
linux-gcp-5.8
Ubuntu:20.04:LTS
linux-gke
Ubuntu:20.04:LTS
linux-gke-5.15
Ubuntu:20.04:LTS
linux-gkeop
Ubuntu:20.04:LTS
linux-gkeop-5.15
fixed in 5.15.0-1003.5~20.04.2
Ubuntu:20.04:LTS
linux-hwe-5.11
Ubuntu:20.04:LTS
linux-hwe-5.13
Ubuntu:20.04:LTS
linux-hwe-5.15
fixed in 5.15.0-33.34~20.04.1
Ubuntu:20.04:LTS
linux-hwe-5.8
Ubuntu:20.04:LTS
linux-ibm
Ubuntu:20.04:LTS
linux-ibm-5.15
fixed in 5.15.0-1033.36~20.04.1
Ubuntu:20.04:LTS
linux-intel-5.13
Ubuntu:20.04:LTS
linux-intel-iotg-5.15
fixed in 5.15.0-1003.5~20.04.1
Ubuntu:20.04:LTS
linux-iot
Ubuntu:20.04:LTS
linux-kvm
Ubuntu:20.04:LTS
linux-lowlatency-hwe-5.15
fixed in 5.15.0-33.34~20.04.1
Ubuntu:20.04:LTS
linux-oem-5.10
Ubuntu:20.04:LTS
linux-oem-5.13
Ubuntu:20.04:LTS
linux-oem-5.14
Ubuntu:20.04:LTS
linux-oem-5.6
Ubuntu:20.04:LTS
linux-oracle
Ubuntu:20.04:LTS
linux-oracle-5.11
📦
Fixed versions by distribution
16The package version that resolves this CVE on each Linux distribution, from the vendor’s published security data. fixed in shows a patched version exists; open means the package is listed as affected with no fix yet.
suse sle15kernel-64kb fixed in 0:5.3.18-150300.59.164.1
suse sle15kernel-default open
suse sle15kernel-default-base fixed in 0:5.3.18-150300.59.164.1.150300.18.96.1
suse sle15kernel-default-devel open
suse sle15kernel-default-livepatch fixed in 0:5.3.18-150300.59.164.1
suse sle15kernel-default-man open
suse sle15kernel-devel open
suse sle15kernel-docs fixed in 0:5.3.18-150300.59.164.1
suse sle15kernel-livepatch-5_3_18-150300_59_164-default fixed in 0:1-150300.7.3.1
suse sle15kernel-macros open
suse sle15kernel-obs-build fixed in 0:5.3.18-150300.59.164.1
suse sle15kernel-preempt fixed in 0:5.3.18-150300.59.164.1
suse sle15kernel-source fixed in 0:5.3.18-150300.59.164.1
suse sle15kernel-syms fixed in 0:5.3.18-150300.59.164.1
suse sle15kernel-zfcpdump fixed in 0:5.3.18-150300.59.164.1
suse sle15reiserfs-kmp-default fixed in 0:5.3.18-150300.59.164.1
▣
Scoring & Timeline
9.1
CRITICAL · CVSS v3.1 · 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Attack Vector
Network
Adjacent
Local
Physical
Attack Complexity
Low
High
Privileges Required
None
Low
High
User Interaction
None
Required
Scope
Unchanged
Changed
Confidentiality
None
Low
High
Integrity
None
Low
High
Availability
None
Low
High
SSVC triage · cisa-vulnrichment
Exploitation
none
Automatable
yes
Technical impact
partial
SSVC asks the questions that actually drive patch urgency: is it being exploited, can attacks be automated, and how total is the impact.
⚑
Vendor Advisories
2suse-csafSUSE-SU-2024:2185-1
suse-csafSUSE-SU-2024:2010-1
🔗
References & Sources
4Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.