CVE-2021-47046
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Weakness
- CWE-193
- Record status
- Analyzed
Affected
- Linux Kernel < 5.10.37
- Linux Kernel < 5.11.21
- Linux Kernel < 5.12.4
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2021-47046.md and follow it. Check whether this project is affected by CVE-2021-47046. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/080bd41d6478a64edf96704fddcda52b1fd5fed7
- https://git.kernel.org/stable/c/403c4528e5887af3deb9838cb77a557631d1e138
- https://git.kernel.org/stable/c/6a58310d5d1e5b02d0fc9b393ba540c9367bced5
- https://git.kernel.org/stable/c/8e6fafd5a22e7a2eb216f5510db7aab54cc545c1
- https://git.kernel.org/stable/c/080bd41d6478a64edf96704fddcda52b1fd5fed7
- https://git.kernel.org/stable/c/403c4528e5887af3deb9838cb77a557631d1e138
- https://git.kernel.org/stable/c/6a58310d5d1e5b02d0fc9b393ba540c9367bced5
- https://git.kernel.org/stable/c/8e6fafd5a22e7a2eb216f5510db7aab54cc545c1
References
- https://git.kernel.org/stable/c/080bd41d6478a64edf96704fddcda52b1fd5fed7
- https://git.kernel.org/stable/c/403c4528e5887af3deb9838cb77a557631d1e138
- https://git.kernel.org/stable/c/6a58310d5d1e5b02d0fc9b393ba540c9367bced5
- https://git.kernel.org/stable/c/8e6fafd5a22e7a2eb216f5510db7aab54cc545c1
- https://git.kernel.org/stable/c/080bd41d6478a64edf96704fddcda52b1fd5fed7
- https://git.kernel.org/stable/c/403c4528e5887af3deb9838cb77a557631d1e138
- https://git.kernel.org/stable/c/6a58310d5d1e5b02d0fc9b393ba540c9367bced5
- https://git.kernel.org/stable/c/8e6fafd5a22e7a2eb216f5510db7aab54cc545c1