# CVE-2026-98782: drm/mediatek: Fix ovl adaptor platform device leak

> A resource leak in the Mediatek DRM driver can lead to memory exhaustion and denial of service if probe or removal paths fail.

- **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-110468, BELL-CVE-2026-98782, DEBIAN-CVE-2026-98782, GHSA-cpv8-j2cq-v3fc, UBUNTU-CVE-2026-98782

## What is CVE-2026-98782?

CVE-2026-98782 is a memory corruption 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: Fix ovl adaptor platform device leak

mtk_drm_probe() creates an OVL adaptor platform device with
platform_device_register_data() when the display pipeline requires the
OVL adaptor.

If a later initialization step fails, the probe error path releases
the DRM resources without unregistering the already registered OVL
adaptor device. The normal remove path likewise leaves the device
registered after the DRM driver is unbound.

Keep track of whether the OVL adaptor was successfully registered and
unregister it on probe failure. Also recover the platform device from
the stored DDP component device and unregister it during normal
removal.

The issue was identified by a static analysis tool I developed and
confirmed by manual review.

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


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

Apply the vendor's patch.

## Is CVE-2026-98782 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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