# CVE-2026-68253: drm/i915/hdcp: check streams[] bounds before overflow

> A buffer overflow in the Linux kernel's i915 HDCP driver allows attackers to corrupt memory, potentially leading to code execution or system crashes.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Aug 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-94842, BELL-CVE-2026-68253, DEBIAN-CVE-2026-68253, GHSA-9cgm-8fj5-jh9j, UBUNTU-CVE-2026-68253

## What is CVE-2026-68253?

CVE-2026-68253 is a high-severity memory corruption vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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)

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2026-68253?


## How do I fix CVE-2026-68253?

Apply the vendor's patch.

## Is CVE-2026-68253 being exploited?

There is no known exploitation of CVE-2026-68253 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-68253 and fix it if it is affected.

What it is: CVE-2026-68253 is a high-severity memory corruption vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-68253 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-68253/ (Markdown: https://insights.sbomify.com/CVE-2026-68253/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-68253
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-68253
- OSV: https://osv.dev/vulnerability/CVE-2026-68253

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-68253/
Summaries are generated and may contain mistakes; the official description above is the record.