# CVE-2026-98783: drm/mediatek: Add missing IS_ERR check for ovl_adaptor platform device

> A missing error check in the Mediatek DRM driver can cause a kernel crash when platform device registration fails, leading to denial of service.

- **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:** 18 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-110471, BELL-CVE-2026-98783, DEBIAN-CVE-2026-98783, GHSA-gxv2-4p27-m9pp, UBUNTU-CVE-2026-98783

## What is CVE-2026-98783?

CVE-2026-98783 is a vulnerability in Linux, published on 18 Oct 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/mediatek: Add missing IS_ERR check for ovl_adaptor platform device

platform_device_register_data() can fail and return an ERR_PTR, but the
return value is used without checking, leading to an invalid pointer
being stored in ddp_comp[].dev and passed to component_match_add() and
mtk_ddp_comp_init(), which could result in a kernel crash.

Add an IS_ERR() check to jump to the error handling path on failure.

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


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

Apply the vendor's patch.

## Is CVE-2026-98783 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98783 is a vulnerability in Linux, published on 18 Oct 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-98783 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-98783/ (Markdown: https://insights.sbomify.com/CVE-2026-98783/index.md)
```

## Sources

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

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