Linux Kernel up to 7.2-rc1 HDCP intel_hdcp.c streams buffer overflow

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.5 | $5k-$25k | 1.05 |
Summary
A vulnerability was found in Linux Kernel up to 6.6.150/6.12.102/6.18.41/7.1.5/7.2-rc1. It has been rated as very critical. The impacted element is an unknown function of the file drivers/gpu/drm/i915/intel_hdcp.c of the component HDCP. This manipulation of the argument streams causes buffer overflow. This vulnerability is registered as CVE-2026-68253. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability has been found in Linux Kernel up to 6.6.150/6.12.102/6.18.41/7.1.5/7.2-rc1 and classified as very critical. Affected by this vulnerability is an unknown function of the file drivers/gpu/drm/i915/intel_hdcp.c of the component HDCP. The manipulation of the argument streams with an unknown input leads to a buffer overflow vulnerability. The CWE definition for the vulnerability is CWE-120. The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer, leading to a buffer overflow. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: drm/i915/hdcp: check streams[] bounds before overflow The data->streams[] overflow check is done after the buffer overflow has already happened. Move the overflow check before the write. Side note, emitting a warning splat with a backtrace might be overkill here, but prefer not changing the behaviour other than not doing the overrun. Discovered using AI-assisted static analysis confirmed by Intel Product Security. (cherry picked from commit 9284ab3b6e776c315883ac2611283d263c9460fd)
The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2026-68253 since 07/30/2026. The exploitation appears to be easy. The attack can be launched remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 08/10/2026).
Upgrading to version 6.6.151, 6.12.103, 6.18.42, 7.1.6 or 7.2-rc2 eliminates this vulnerability. Applying the patch 84351f12390349ba010920fc247e1a0b12e41eb3/2106fb490b2c6003e23ad6ff36ce823a2170e138/3d2ef8d389495e7889c6062d8bddc46d2a5fbdef/984085c5b53572e2e03fd5fc4817e86ef1effc6e/bbb15a6b042d02e5508a02b4847e02d2579ee7bc is able to eliminate this problem.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
- 6.6.150
- 6.12.102
- 6.18.0
- 6.18.1
- 6.18.2
- 6.18.3
- 6.18.4
- 6.18.5
- 6.18.6
- 6.18.7
- 6.18.8
- 6.18.9
- 6.18.10
- 6.18.11
- 6.18.12
- 6.18.13
- 6.18.14
- 6.18.15
- 6.18.16
- 6.18.17
- 6.18.18
- 6.18.19
- 6.18.20
- 6.18.21
- 6.18.22
- 6.18.23
- 6.18.24
- 6.18.25
- 6.18.26
- 6.18.27
- 6.18.28
- 6.18.29
- 6.18.30
- 6.18.31
- 6.18.32
- 6.18.33
- 6.18.34
- 6.18.35
- 6.18.36
- 6.18.37
- 6.18.38
- 6.18.39
- 6.18.40
- 6.18.41
- 7.1.0
- 7.1.1
- 7.1.2
- 7.1.3
- 7.1.4
- 7.1.5
- 7.2-rc1
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.9VulDB Meta Temp Score: 9.5
VulDB Base Score: 9.9
VulDB Temp Score: 9.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Buffer overflowCWE: CWE-120 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 6.6.151/6.12.103/6.18.42/7.1.6/7.2-rc2
Patch: 84351f12390349ba010920fc247e1a0b12e41eb3/2106fb490b2c6003e23ad6ff36ce823a2170e138/3d2ef8d389495e7889c6062d8bddc46d2a5fbdef/984085c5b53572e2e03fd5fc4817e86ef1effc6e/bbb15a6b042d02e5508a02b4847e02d2579ee7bc
Timeline
07/30/2026 CVE reserved08/10/2026 Advisory disclosed
08/10/2026 VulDB entry created
08/10/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2026-68253 (🔒)
GCVE (CVE): GCVE-0-2026-68253
GCVE (VulDB): GCVE-100-387625
Entry
Created: 08/10/2026 16:52Changes: 08/10/2026 16:52 (60)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.