# CVE-2026-68247: drm/i915/bios: range check LFP Data Block panel_type2

> Missing range check in Intel i915 BIOS parsing allows local attackers to cause a denial of service via malformed panel type data.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Aug 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-94835, BELL-CVE-2026-68247, DEBIAN-CVE-2026-68247, GHSA-7xvp-vq9h-5h28, UBUNTU-CVE-2026-68247

## What is CVE-2026-68247?

CVE-2026-68247 is a 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/bios: range check LFP Data Block panel_type2

While the panel_type from LFP Data Block is range checked, panel_type2
is not. Add a few helpers for range checking, and use them to not only
check panel_type2, but also improve clarity and correctness in the panel
type selection.

Discovered using AI-assisted static analysis confirmed by Intel Product
Security.

v2:
- Fix commit message typo (Michał)
- Add is_panel_type_pnp() (Ville)

(cherry picked from commit c9ebe5d2f25729d6cfbbb1235d640bf67f9275df)

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


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

Apply the vendor's patch.

## Is CVE-2026-68247 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-68247 is a 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-68247 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-68247/ (Markdown: https://insights.sbomify.com/CVE-2026-68247/index.md)
```

## Sources

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

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