CVE-2021-47046: drm/amd/display: Fix off by one in hdmi_14_process_transaction()
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 080bd41d6478a64edf96704fddcda52b1fd5fed7, 403c4528e5887af3deb9838cb77a557631d1e138, 6a58310d5d1e5b02d0fc9b393ba540c9367bced5.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 080bd41d6478a64edf96704fddcda52b1fd5fed7, 403c4528e5887af3deb9838cb77a557631d1e138, 6a58310d5d1e5b02d0fc9b393ba540c9367bced5 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix off by one in hdmi_14_process_transaction() The hdcp_i2c_offsets[] array did not have an entry for HDCP_MESSAGE_ID_WRITE_CONTENT_STREAM_TYPE so it led to an off by one read overflow. I added an entry and copied the 0x0 value for the offset from similar code in drivers/gpu/drm/amd/display/modules/hdcp/hdcp_ddc.c. I also declared several of these arrays as having HDCP_MESSAGE_ID_MAX entries. This doesn't change the code, but it's just a belt and suspenders approach to try future proof the code.
- Published
- Feb 28, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- CWE-193
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.5affected
- 4c283fdac08abf3211533f70623c90a34f41d08d and later · before 403c4528e5887af3deb9838cb77a557631d1e138affected · git
- 4c283fdac08abf3211533f70623c90a34f41d08d and later · before 6a58310d5d1e5b02d0fc9b393ba540c9367bced5affected · git
- 4c283fdac08abf3211533f70623c90a34f41d08d and later · before 080bd41d6478a64edf96704fddcda52b1fd5fed7affected · git
- 4c283fdac08abf3211533f70623c90a34f41d08d and later · before 8e6fafd5a22e7a2eb216f5510db7aab54cc545c1affected · git
- before 5.5not affected · semver
- 5.10.37 and later · up to and including 5.10.*not affected · semver
- 5.11.21 and later · up to and including 5.11.*not affected · semver
- 5.12.4 and later · up to and including 5.12.*not affected · semver
- 5.13 and laternot affected · original_commit_for_fix
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.5 and later · before 5.10.37
- linux linux kernel5.11 and later · before 5.11.21
- linux linux kernel5.12 and later · before 5.12.4
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 5.10.38-1 | 5.10.38-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2021-47044Feb 28, 2024 · sched/fair: Fix shift-out-of-bounds in load_balance()30Monitor
- ← EarlierCVE-2021-47045Feb 28, 2024 · scsi: lpfc: Fix null pointer dereference in lpfc_prep_els_iocb()22Monitor
- Later →CVE-2021-47047Feb 28, 2024 · spi: spi-zynqmp-gqspi: return -ENOMEM if dma_map_single fails22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 080bd41d6478a64edf96704fddcda52b1fd5fed7 | Vendor (CNA) |
| Linux Linux | 403c4528e5887af3deb9838cb77a557631d1e138 | Vendor (CNA) |
| Linux Linux | 6a58310d5d1e5b02d0fc9b393ba540c9367bced5 | Vendor (CNA) |
| Linux Linux | 8e6fafd5a22e7a2eb216f5510db7aab54cc545c1 | Vendor (CNA) |
| debian:linux | 5.10.38-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2023-38429226 days apartAn issue was discovered in the Linux kernel before 6.3.4.39Monitor
- CVE-2024-2699563 days apartusb: typec: tcpm: Correct the PDO counting in pd_set31Monitor
- CVE-2022-4867265 days apartof: fdt: fix off-by-one error in unflatten_dt_nodes()31Monitor
- CVE-2022-48732113 days apartdrm/nouveau: fix off by one in BIOS boundary checking31Monitor
- CVE-2024-43852171 days aparthwmon: (ltc2991) re-order conditions to fix off by one bug31Monitor
- CVE-2024-46852212 days apartdma-buf: heaps: Fix off-by-one in CMA heap fault handler31Monitor
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0145 · Feb 29, 2024(Linux Kernel Güncellemesi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-193 · Off-by-one ErrorCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.